Dashboard services widget error?

jlepthien

Hi there,

this really isn't that important but I thought I'd just tell you about it. Under Status->Services I see the following:

avahi Not available. Running
dnsmasq DNS Forwarder Running
ntpd NTP clock sync Running
dhcpd DHCP Service Running
igmpproxy Not available. Stopped
racoon IPsec VPN Running

When I add the services widget to the dashboard though I only see these services:

avahi Not available. Running
dnsmasq DNS Forwarder Running
dhcpd DHCP Service Running
racoon IPsec VPN Running

Why is that? NTP is missing and also my not running service. Is this on purpose?

I am running the build from the 19th for 4G embedded btw….

jimp

I also don't see the ntpd process there. I'll have to check the code, but I seem to recall skipping something.
I know I have that setting that will allow you to filter out ones you don't want to see, but I don't recall if that skipped any by default.

jimp

I just committed a fix which sync's the widget up with the correct code for 2.0's services status page. It fixes things for me with ntpd, but I didn't try igmpproxy. Non-running services should show up fine. On my test box I have blinkled installed but not configured so it isn't running and it shows up OK.

It should work on the next snap after now, or with a gitsync (or if you apply the patch by hand…)

jlepthien

Thanks jimp. I will wait for the next snap.

jlepthien

Hey jimp. Thanks. Now all services are shown, also the ones stopped! ;)

geeknik

Ever since I upgraded to the 1/20 build of 2.0-BETA, several services are showing as not started after an upgrade/reboot. This is also including 2.0-BETA1 built on Fri Jan 22 08:25:58 EST 2010. I just upgraded, rebooted and the only service showing that it was running was ntpd. Miniupnpd, dnsmasq and dhcpd were shown as not started, and I verified they weren't started because no machine on the LAN was able to resolve DNS. They started fine when I clicked the start button, but shouldn't they start automatically?

jimp

They should, yes, but this topic is for the status showing incorrectly in the dashboard widget. That is, they were running as they should but the status was wrong.

If they are really not starting for you, that should be a new issue in a separate thread.