system init failed, wviewd.pid exists,

826 views
Skip to first unread message

nbsky

unread,
May 17, 2012, 6:37:31 PM5/17/12
to wview
Hi Everyone,

I actually think I know what I did wrong but I need some help to
correct what I did without reinstalling my entire NSLU2's software.

What I did was try to install wview using the source file and when
this didn't work and when the "apt-get" for 5.20.0 became available I
installed wview via apt-get. Everything worked fine for over a month
and then I noticed weather underground was not updating. I restarted
the NSLU2 and started wview and the following is the error I
received.

wthr:~# /etc/init.d/wview start
Starting wview daemons:
wviewd[3283]: <1337214690201> : lock file /var/lib/wview/wviewd.pid
exists, older copy may be running - aborting!
wviewd[3283]: <1337214690208> : system init failed!

I purged wview install and then reinstalled using apt-get. Everything
worked great again for about 15 days and then I had the same failure.
I find it odd that it runs for a while and then stops.

Any help would be much appreciated.

Alan

unread,
May 18, 2012, 11:27:26 AM5/18/12
to wv...@googlegroups.com
Unfortunately, that information alone isn't enough to tell us why the failure occurred.  What it DOES say is that the wviewd daemon aborted unexpectedly and left it's PID (process ID) file on the filesystem.  If you remove /var/lib/wview/wviewd.pid by hand and then restart it should come up OK.  You shouldn't need to purge and reinstall the software.

But you might want to check your /var/log/system.log (or /var/log/wview.log if it exists) and look for lines with "wviewd" in them.  If you're lucky, you might see something that will help to determine the cause of wviewd aborting.

Hope this helps...

nbsky

unread,
May 18, 2012, 9:55:05 PM5/18/12
to wview
Alan,

Thank you for the suggestion on deleting the wview.pid file. Wview is
up and running again but now to find why wviewd is aborting. My
wview.log file was 0.5 mb so I deleted it and will wait for wviewd to
abort again and then do some more research. I'll keep an eye on the
log files. Thank you for the help.
Reply all
Reply to author
Forward
0 new messages