В Fri, 15 Feb 2013 17:37:44 +0100 Claudio ML <claudioml@mediaservice.net> пишет:

Hello all,

Some problems here with snmpd and systemd on OpenSuSE 12.2.

systemctl start snmpd.service systemctl status snmpd.service snmpd.service - snmpd Loaded: loaded (/lib/systemd/system/snmpd.service; linked) Active: inactive (dead) since Fri, 15 Feb 2013 18:15:39 +0100; 1s ago Process: 20099 ExecStart=/usr/sbin/snmpd (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/snmpd.service

Please open bug report (or search for one if it exists) and post number here. I'll get a look (it is clear what happens, the question is how to make minimal change suitable for stable update).

No trace in the logs of what happening. The same config on an OpenSuSE pre-systemd (11.4), works perfectly. And, if i try to start it manually, it works.

Question: how to debug that problem? Other Question: generally, how to debug systemd startup problems? Any info about this is welcome.

Cordially,

Claudio Prono.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Claudio ML said the following on 02/15/2013 11:37 AM:

Hello all,

Some problems here with snmpd and systemd on OpenSuSE 12.2.

systemctl start snmpd.service systemctl status snmpd.service snmpd.service - snmpd Loaded: loaded (/lib/systemd/system/snmpd.service; linked) Active: inactive (dead) since Fri, 15 Feb 2013 18:15:39 +0100; 1s ago Process: 20099 ExecStart=/usr/sbin/snmpd (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/snmpd.service

No trace in the logs of what happening. The same config on an OpenSuSE pre-systemd (11.4), works perfectly. And, if i try to start it manually, it works.

When I've had problems with services it has always come down to one of two things. The first was time-out. Part of my spam handling is that I use Peter Lowe's DNS based adblocking. See http://pgl.yoyo.org/ Loading all those null addresses takes time. OUCH! When I first converted to systemd my DNS always timed out and things that depended on DNS, notably SMTP/Postfix, failed. Easy to fix; its in the documentation. The second, and I think that is what applies in your case, had to do with missing dependencies. In my case I found spamassassin.service was failing on boot but could be started manually. This was resolved by making it dependent on DNS so that the Razor and other network based sources of spam information could be accessed by name. In 11.4 the start-up was sequential; timeout was never an issue since there was no 'manager' as such - each script ran to completion, and the sequence determined dependencies. I don't use SNMP so I can't tell you what the dependency is. Debug? This is really a 'think about it' problem. What is SMTP going to be dependent on? You might try running 'systemctl status snmpd.service' after it is running; it _might_ give some hints. Then again if your old 11.4 system is around you can see what there was in init3 or init5 that was done sequentially before SNMP. Most problems with systemd are, in my experience, solved by thought and inspection. It all comes down to looking at the start-up as a tree where the branches can run in parallel. I do a lot of mind-mapping and the idea of a 'target' (which I'd put as the root on the right) and all the things that contribute to reaching that target as branches to the left, as if they flow into it, is a very common mind-map model. Perhaps because this conceptualization comes easily to me is why I don't have problems with systemd where other people do. -- A rock has no detectable opinion about gravity. -- _The Science of Discworld_ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org