Scribe scribe 3.x_y - syslog-ng and logrotate installer

[visortgw]

Since updating to 3.0.0 and further to 3.0.2 uiscribe is extremely laggy - as in sections of the General Log page going missing when I scroll and returning after either around 10 seconds or a manual refresh. Is this a product of the changes to scribe or is uiscribe due an update?
The above is constant no matter what I try.

I don't see this on my GT-AX6000.

 

[cmkelley]

I actually tried this as a test. I edited scribe_menu() within scribe v3.0_2 as follows:

rs)
    menu_restart
    menu_status
    ;;
st)
    if sng_rng
    then
        menu_stop
    else
        not_recog=true
    fi
    ;;

becomes

rs)
    if sng_rng
    then
        menu_stop
    else
        not_recog=true
    fi
    menu_restart
    menu_status
    ;;
st)
    if sng_rng
    then
        menu_stop
    else
        not_recog=true
    fi
    ;;

Output from execution of NEW "rs." from menu:

Please select an option: rs
 stopping syslog-ng ... Checking syslog-ng...              alive.
 Shutting down syslog-ng...              done.
 starting system klogd and syslogd ...
Done.

 syslog-ng will be started at next reboot; you
 may type 'scribe restart' at shell prompt, or
 select rs from scribe menu to restart syslog-ng


 syslog-ng NOT running!  Starting  ...
 Starting syslog-ng...              done.
 Restarting uiScribe ...Mounting WebUI page for uiScribe

Mounted uiScribe WebUI page as Main_LogStatus_Content.asp


      checking syslog-ng daemon ... alive.

 checking system for necessary scribe hooks ...

          checking S01syslog-ng ... present.
         checking service-event ... present.
            checking post-mount ... present.
               checking unmount ... present.
    checking logrotate cron job ... updated.
       checking directory links ... present.

 checking syslog-ng configuration ...

   syslog-ng.conf version check ... in sync. (3.38)
    syslog-ng.conf syntax check ... okay!

          scribe installed version: v3.0_2 (master)
             scribe GitHub version: v3.0_2 (master)
                 Minor scribe update available

 Press [Enter] to continue:

No error(s) thrown! Files/symbolic links intact:

# pwd
/jffs
# ls -al syslog*
lrwxrwxrwx    1 TheS1R   root            21 Apr 26 08:50 syslog.log -> /opt/var/log/messages
-rw-rw-rw-    1 TheS1R   root            24 Apr 26 08:50 syslog.log-1

And that's what I get for not being able to test on a router before publishing. I tried to do the same thing, only in the menu_restart routine, and "it looked good from my house." If someone wants to make a pull request, at least that I can accept from work.

In addition to your change, in the menu_restart, change

menu_restart(){
    if sng_rng
    then
        printf "\n$yellow Restarting %s... $std\n" "$sng"
        $S01sng_init stop
        $S01sng_init start
    else
        printf "\n$white %s$red NOT$white running! $yellow Starting %s ... $std\n" "$sng"
        $S01sng_init start
    fi
    hup_uisc
}

to:

menu_restart(){
    if sng_rng
    then
        printf "\n$yellow Restarting %s... $std\n" "$sng"
        $S01sng_init restart
    else
        printf "\n$white %s$red NOT$white running! $yellow Starting %s ... $std\n" "$sng"
        $S01sng_init start
    fi
    hup_uisc
}

One other piece of information that might help, with syslog-ng running (and the links correct) try

/opt/etec/init.d/S01sylog-ng restart

and tell me if that messes up the links. I'm pretty sure it will, but would like to verify.

Ours is fast coming up on 5 years.

Thanks!

 

[cmkelley]

Nor should we!
Don't sweat it, approach it with fresh eyes when you get the time and I'm sure you'll crack it.
It's meant to be a fun learning exercise, remember?

Yes, it is supposed to be a fun learning exercise, but it bugs me it's causing problems for people. And annoying I can't directly test at home to see if my "fixes" are working, which so far they ain't.

 

[cmkelley]

I don't see this on my GT-AX6000.

Do you see if if the links are hosed up?

 

[cmkelley]

Enjoy your time with your granddaughter!

(That‘s not an obligation at all, I think)

True, it's not. It's really more of a favor to my wife, who loathes driving at night, so if granddaughter goes home after dark, I drive. And yeah, she's tons of fun, and of course the cutest thing you ever saw!

 

[visortgw]

One other piece of information that might help, with syslog-ng running (and the links correct) try

/opt/etec/init.d/S01sylog-ng restart

and tell me if that messes up the links. I'm pretty sure it will, but would like to verify.

Ours is fast coming up on 5 years.

Thanks!

Yes, it kills the links (but the modified "rs." fixes them):

# cd /opt/etc/init.d
TheS1R@GT-AX6000-9980:/tmp/mnt/TheS1RsUSB/entware/etc/init.d# ./S01syslog-ng restart
 Shutting down syslog-ng...              done.
 Starting syslog-ng...              done.
TheS1R@GT-AX6000-9980:/tmp/mnt/TheS1RsUSB/entware/etc/init.d# cd /jffs
TheS1R@GT-AX6000-9980:/jffs# ls -al syslog*
syslog.log:
drwxrwxrwx    2 TheS1R   root           160 Apr 26 09:42 .
drwxr-xr-x   17 TheS1R   root          1992 Apr 26 09:42 ..

syslog.log-1:
drwxrwxrwx    2 TheS1R   root           160 Apr 26 09:42 .
drwxr-xr-x   17 TheS1R   root          1992 Apr 26 09:42

Give me a minute to make the other code changes.

 

[visortgw]

Do you see if if the links are hosed up?

No.

 

[visortgw]

And that's what I get for not being able to test on a router before publishing. I tried to do the same thing, only in the menu_restart routine, and "it looked good from my house." If someone wants to make a pull request, at least that I can accept from work.

In addition to your change, in the menu_restart, change

menu_restart(){
    if sng_rng
    then
        printf "\n$yellow Restarting %s... $std\n" "$sng"
        $S01sng_init stop
        $S01sng_init start
    else
        printf "\n$white %s$red NOT$white running! $yellow Starting %s ... $std\n" "$sng"
        $S01sng_init start
    fi
    hup_uisc
}

to:

menu_restart(){
    if sng_rng
    then
        printf "\n$yellow Restarting %s... $std\n" "$sng"
        $S01sng_init restart
    else
        printf "\n$white %s$red NOT$white running! $yellow Starting %s ... $std\n" "$sng"
        $S01sng_init start
    fi
    hup_uisc
}

"rs." still does not kill symbolic links after the additional changes. Any other test(s) that you need me to run?

 

[cmkelley]

"rs." still does not kill symbolic links after the additional changes. Any other test(s) that you need me to run?

Wait, what? It's broken again after changing the stop / start to restart in menu_restart? Whaaaaaaaaaaa ?????

 

[visortgw]

Wait, what? It's broken again after changing the stop / start to restart in menu_restart? Whaaaaaaaaaaa ?????

NO, not broken -- it works. It does NOT kill symbolic links.

 

[cmkelley]

NO, not broken -- it works. It does NOT kill symbolic links.

Oh, WHEW! I misunderstood you. That's a relief.

 

[visortgw]

Oh, WHEW! I misunderstood you. That's a relief.

Just offering to run any additional test(s) that you can't run yourself...

 

[ColDen]

V3.0_2 is also working OK here:

Thanks!

 

[elorimer]

Since updating to 3.0.0 and further to 3.0.2 uiscribe is extremely laggy - as in sections of the General Log page going missing when I scroll and returning after either around 10 seconds or a manual refresh. Is this a product of the changes to scribe or is uiscribe due an update?
The above is constant no matter what I try.

In my experience (because this often happens to me) this is almost always a logrotate problem. Any log file over 1mb is going to bring everything other than messages to a halt, even if you are not showing it.

 

[Ripshod]

In my experience (because this often happens to me) this is almost always a logrotate problem. Any log file over 1mb is going to bring everything other than messages to a halt, even if you are not showing it.

I've reinstalled both with no change. However, with this advice I've disabled firewall logging as that's the log file with the most activity (the others are lucky to get thirty entries an hour). Will see what happens.

 

[visortgw]

I've reinstalled both with no change. However, with this advice I've disabled firewall logging as that's the log file with the most activity (the others are lucky to get thirty entries an hour). Will see what happens.

Might it be caused by slow USB flash drive? I suggest using real SSD USB drive or SSD drive installed in USB enclosure rather than cheap USB flash drive.

 

[Ripshod]

I have a Kingston SSD running right now (for about 6 months) so I can't see that being the problem. I never had an issue until the 3.0.0 update. I did a rebuild for the 388.1 merlin firmware but skipped it with the 388.2

ETA:
First time I've seen this. It's repeated over and over in the logs.

Apr 26 15:53:37 ripshod syslog-ng[28253]: syslog-ng starting up; version='3.38.1'
Apr 26 18:07:16 ripshod syslog-ng[28253]: The current log file has a mismatching size/inode information, restarting from the beginning; state='affile_sd_curpos(/var/lib/logrotate.status)', stored_inode='61692', cur_file_inode='911502', stored_size='208', cur_file_size='253', raw_stream_pos='0'
Apr 26 18:07:16 ripshod syslog-ng[28253]: The current log file has a mismatching size/inode information, restarting from the beginning; state='affile_sd_curpos(/opt/tmp/logrotate.daily)', stored_inode='6293400', cur_file_inode='6292495', stored_size='0', cur_file_size='88', raw_stream_pos='0'

Other logs are mentioned too.

 

[Ripshod]

I have a Kingston SSD running right now (for about 6 months) so I can't see that being the problem. I never had an issue until the 3.0.0 update. I did a rebuild for the 388.1 merlin firmware but skipped it with the 388.2

ETA:
First time I've seen this. It's repeated over and over in the logs.

Apr 26 15:53:37 ripshod syslog-ng[28253]: syslog-ng starting up; version='3.38.1'
Apr 26 18:07:16 ripshod syslog-ng[28253]: The current log file has a mismatching size/inode information, restarting from the beginning; state='affile_sd_curpos(/var/lib/logrotate.status)', stored_inode='61692', cur_file_inode='911502', stored_size='208', cur_file_size='253', raw_stream_pos='0'
Apr 26 18:07:16 ripshod syslog-ng[28253]: The current log file has a mismatching size/inode information, restarting from the beginning; state='affile_sd_curpos(/opt/tmp/logrotate.daily)', stored_inode='6293400', cur_file_inode='6292495', stored_size='0', cur_file_size='88', raw_stream_pos='0'

Other logs are mentioned too.

Fixed with a reset and minimal install. Gonna add things back no and check, but panic over.

 

[visortgw]

I have a Kingston SSD running right now (for about 6 months) so I can't see that being the problem. I never had an issue until the 3.0.0 update. I did a rebuild for the 388.1 merlin firmware but skipped it with the 388.2

ETA:
First time I've seen this. It's repeated over and over in the logs.

Apr 26 15:53:37 ripshod syslog-ng[28253]: syslog-ng starting up; version='3.38.1'
Apr 26 18:07:16 ripshod syslog-ng[28253]: The current log file has a mismatching size/inode information, restarting from the beginning; state='affile_sd_curpos(/var/lib/logrotate.status)', stored_inode='61692', cur_file_inode='911502', stored_size='208', cur_file_size='253', raw_stream_pos='0'
Apr 26 18:07:16 ripshod syslog-ng[28253]: The current log file has a mismatching size/inode information, restarting from the beginning; state='affile_sd_curpos(/opt/tmp/logrotate.daily)', stored_inode='6293400', cur_file_inode='6292495', stored_size='0', cur_file_size='88', raw_stream_pos='0'

Other logs are mentioned too.

Almost looks like corrupted external disk...

 

[Ripshod]

Almost looks like corrupted external disk...

I think you're right. I've reinstalled virtually everything and it hasn't missed a beat. These logs are sooooo quiet now it's a little unnerving.
Thanks for your hard work @cmkelley!