Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 3 subscribers
  • Views 406 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

dashboard reports

asgnewbie
hello fellas,

i have asg220 running on 7.405 the problem is no reports being displayed in dashboard,i updated it to ver 7.503 hoping that it could fix my problem but still no glory.
I checked the http logs and it shows some logs being access from the web

if somebody encountered and solved this issue
pls post here your procedure.

thanks


This thread was automatically locked due to age.
Parents
  • 0 in reply to BAlfson
    Hi,
    I tried these procedures
    When I perform these commands no error occured.
    ****************************************************
    Iive had this problem too. I've updated to v7.301 and still have the problem. 

    I droped the table and recreated it via the above instructions, and it seems good now. 

    Specifically the instructions are:
    1.) /etc/init.d/ulog stop
    2.) /etc/init.d/syslogng stop
    3.) /var/storage/pgsql/init/reporting_db_init.sh
    4.) /etc/init.d/syslogng start
    5.) /etc/init.d/ulog start

    Function complete. 


    ***************************************
    I want to perform these commands suggested by xXlAinXx  but Im afraid
    becuse Im newbie also to linux command

    # sudo su

    # /etc/init.d/ulog stop
    # /etc/init.d/syslogng stop

    # cd /var/log/reporting/pgsql/ 
    # mv 16*** /home


    # su - postgres

    > /var/storage/pgsql/init/reporting_db_init.sh

    # su root
    # /etc/init.d/syslogng start
    # /etc/init.d/ulog start

    # test -x /usr/local/bin/snort-cleanup && /usr/local/bin/snort-cleanup
    # /usr/local/bin/report_render.plx --sendmail

    # reboot
Reply
  • 0 in reply to BAlfson
    Hi,
    I tried these procedures
    When I perform these commands no error occured.
    ****************************************************
    Iive had this problem too. I've updated to v7.301 and still have the problem. 

    I droped the table and recreated it via the above instructions, and it seems good now. 

    Specifically the instructions are:
    1.) /etc/init.d/ulog stop
    2.) /etc/init.d/syslogng stop
    3.) /var/storage/pgsql/init/reporting_db_init.sh
    4.) /etc/init.d/syslogng start
    5.) /etc/init.d/ulog start

    Function complete. 


    ***************************************
    I want to perform these commands suggested by xXlAinXx  but Im afraid
    becuse Im newbie also to linux command

    # sudo su

    # /etc/init.d/ulog stop
    # /etc/init.d/syslogng stop

    # cd /var/log/reporting/pgsql/ 
    # mv 16*** /home


    # su - postgres

    > /var/storage/pgsql/init/reporting_db_init.sh

    # su root
    # /etc/init.d/syslogng start
    # /etc/init.d/ulog start

    # test -x /usr/local/bin/snort-cleanup && /usr/local/bin/snort-cleanup
    # /usr/local/bin/report_render.plx --sendmail

    # reboot
Children
  • 0 in reply to asgnewbie
    I want to perform these commands suggested by xXlAinXx  but Im afraid
    becuse Im newbie also to linux command


    That's what backups are for.

    However, since you have an appliance, you probably have a support contract... in which case you could open a support case with your reseller.

    Barry