Log errors explained?

lourens.henk · June 6, 2011, 9:04pm

I just ran a “logread”
(note to self… have it posted to the shell command thread ;D)

i encounterd a continously recurring error:

/Rotate_Logs.sh Jun 6 22:55:01 MiOS_2xxx cron.err crond[925]: USER root pid 32529 cmd /usr/bin

Seems my logrotation creates a cron error… anyone able to explain more to me?

–edit–
All i could find was this OpenWRT reference:
https://forum.openwrt.org/viewtopic.php?id=25225
http://svn.dd-wrt.com/browser/src/router/busybox/miscutils/crond.c?rev=11061

See also this thread where more errors show:
http://forum.mios.com/index.php?topic=6335

guessed · June 7, 2011, 2:35pm

Henk,
[tt]logread[/tt] is a standard part of OpenWRT, but what you log into it is up to the apps running on the box. In this case, [tt]Rotate_Logs.sh[/tt] is a script from MiOS.

It wakes every minute (roughly) and works out if it needs to log anything, terminating if not. Since this script is run by [tt]cron[/tt], a standard Unix scheduling module, that reports the error code.

Eventually the log rotation itself kicks in, and you’ll see log lines like:

Jun 7 04:21:01 MiOS_1xxxx cron.err crond[987]: USER root pid 11912 cmd /usr/bin/Rotate_Logs.sh Jun 7 04:22:01 MiOS_1xxxx cron.err crond[987]: USER root pid 12048 cmd /usr/bin/Rotate_Logs.sh Jun 7 04:23:01 MiOS_16577 cron.err crond[987]: USER root pid 12208 cmd /usr/bin/Rotate_Logs.sh Jun 7 04:24:01 MiOS_1xxxx cron.err crond[987]: USER root pid 12345 cmd /usr/bin/Rotate_Logs.sh Jun 7 04:24:02 MiOS_16577 user.notice Rotate_Logs[12346]: SYSROTATE: Starting Jun 7 04:25:01 MiOS_1xxxx cron.err crond[987]: user root: process already running: /usr/bin/Rotate_Logs.sh Jun 7 04:25:16 MiOS_1xxxx user.notice Rotate_Logs[12346]: SYSROTATE: done at: 2011-06-07_04-24-01 Jun 7 04:26:01 MiOS_16577 cron.err crond[987]: USER root pid 12782 cmd /usr/bin/Rotate_Logs.sh Jun 7 04:27:01 MiOS_1xxxx cron.err crond[987]: USER root pid 12918 cmd /usr/bin/Rotate_Logs.sh

This type of question is safe to post in the general forum, where you might get others responding. There’s nothing sensitive in what’s being asked.

conchordian · February 25, 2013, 1:32am

I’m getting quite a few errors in my log, but when I click on the envelope/letter to read them, Vera says ‘please wait’, but nothing happens.

I’ve tried http://VERAIP/cgi-bin/cmh/log.sh?Device=LuaUPnP, but it seems to be real time, rather than letting me look for the errors.

Is this normal?

Thanks

guessed · February 25, 2013, 1:36am

The URL-based log access only shows “current” stuff. If you want to look back at the historical stuff, then you need to SSH into Vera itself and look at [tt]/var/log/cmh/LuaUPnP.log[/tt] directly.

Even then, this log file rotates out fairly frequently (depends upon log level) so you won’t be able to go back too far.

conchordian · February 25, 2013, 2:09am

OK, was hoping to avoid the SSH stuff. Is there a plugin which displays the lualuup.log, by any chance?

When I click the envelope icon, as pictured in my screencapture, is something supposed to happen?

Thank you.

guessed · February 25, 2013, 2:13am

You can also use WinSCP to copy the LuaUPnP.log file out. You still need the login credentials, the same ones you’d use if you were SSH’ing in, but it’s a GUI interface to copy the files out.

Each time I’ve tried that UI, I’ve found it to be woefully incomplete so I stopped using it.

conchordian · February 25, 2013, 4:11am

Thank you, I can’t seem to get into it with putty or winscp.

I ran the code here: http://forum.micasaverde.com/index.php/topic,7110.msg62534.html#msg62534 which told me my password, which is the same as my wifi one on the bottom of the Vera, but it still won’t login.

I’ve forwarded port 22 to my Vera’s IP, but I’m trying to access it locally so that shouldn’t matter.

futzle · February 25, 2013, 4:17am

Turn that off immediately, unless your plan is to let the world figure out your root password for you.

guessed · February 25, 2013, 4:32am

If you’ve ever reset Vera’s password to something custom, then that technique won’t work.

You may be able to use the “remote” account, outlined in this note:
http://wiki.micasaverde.com/index.php/Logon_Vera_SSH#Can.27t_find_the_root_password.3F

and use it to “reset” the password of the “root” account (either with passwd root, or by editing the /etc/passwd file directly (after making a backup, of course)

conchordian · February 25, 2013, 4:57am

Yeah, I did when it made no difference, but thanks for the heads up.

So using your code, thanks, and the enable tech support trick (http://wiki.micasaverde.com/index.php/Logon_Vera_SSH#Can.27t_find_the_root_password.3F), both tell me my password is the wifi one and yet I can’t login.

[quote=“guessed, post:9, topic:168469”]If you’ve ever reset Vera’s password to something custom, then that technique won’t work.

You may be able to use the “remote” account, outlined in this note:
http://wiki.micasaverde.com/index.php/Logon_Vera_SSH#Can.27t_find_the_root_password.3F

and use it to “reset” the password of the “root” account (either with passwd root, or by editing the /etc/passwd file directly (after making a backup, of course)[/quote]

Thanks a lot, passwd root did the trick and that winscp program made it easy to access the log. Now to decipher it!

conchordian · February 26, 2013, 4:14am

I think it may be Vacation Ghost, it seems to be logging quite often:

50 02/26/13 13:49:14.106 luup_log:142: VGinfo: Calling main loop with lul_device: 142 <0x2da5e680>
50 02/26/13 13:49:14.107 luup_log:142: VGinitPhase: VacationGhost is disabled, sleep and start over <0x2da5e680>
06 02/26/13 13:49:14.108 Device_Variable::m_szValue_set device: 142 service: urn:upnp-org:serviceId:VGhost1 variable: e[35;1mStatee[0m was: 0 now: 0 #hooks: 0 upnp: 0 v:0xe5ced8/NONE duplicate:1 <0x2da5e680>