forum.opsi.org

hi again

after we fixed the OS deployment issues, we ran into a new problem. we tried to create a depot server - after the call of the /usr/share/opsi/register-depot.py script it seemed that everything OK. the depot server has registered in the central OPSI server (it appeared on the management interface too), but after the reboot of the depot server, everything gone wrong. after a while the server became unresponsive and the kernel flooded the shell with some messages (attachment #1 and #2). after reseting of the server, i found the next lines in the /var/los/opsi/opsiconfd/opsiconfd.log:

==================================================================
OPSI configuration-service starting
==================================================================
(opsiconfd|1418)
[4] [Nov 15 23:06:15] Added static content '/' which points to directory '/usr/share/opsiconfd/static' (opsiconfd|1216)
[4] [Nov 15 23:06:16] Added webdav content 'opsi-depot' which points to directory '/opt/pcbin/install' (opsiconfd|1243)
[4] [Nov 15 23:06:16] Added static content 'configed' which points to directory '/usr/lib/configed' (opsiconfd|1238)
[1] [Nov 15 23:06:17] Traceback: (Logger.py|648)
[1] [Nov 15 23:06:17] line 1500 in '<module>' in file '/usr/sbin/opsiconfd' (Logger.py|648)
[1] [Nov 15 23:06:17] line 1445 in 'main' in file '/usr/sbin/opsiconfd' (Logger.py|648)
[1] [Nov 15 23:06:17] line 1248 in 'createRoot' in file '/usr/sbin/opsiconfd' (Logger.py|648)
[1] [Nov 15 23:06:17] line 671 in 'getDepot_hash' in file '/etc/opsi/backendManager.d/50_interface.conf' (Logger.py|648)
[1] [Nov 15 23:06:17] line 501 in '_execMethod' in file '/var/lib/python-support/python2.5/OPSI/Backend/BackendManager.py' (Logger.py|648)
[1] [Nov 15 23:06:17] line 1 in '<module>' in file '<string>' (Logger.py|648)
[1] [Nov 15 23:06:17] line 3 in 'getDepot_hash' in file '<string>' (Logger.py|648)
[1] [Nov 15 23:06:17] line 262 in '_jsonRPC' in file '/var/lib/python-support/python2.5/OPSI/Backend/JSONRPC.py' (Logger.py|648)
[1] [Nov 15 23:06:17] ==>>> (-2, 'Name or service not known') (opsiconfd|1516)
[2] [Nov 15 23:06:17] ERROR: (opsiconfd|1517)
[2] [Nov 15 23:06:17] (opsiconfd|1517)
[2] [Nov 15 23:06:17] (-2, 'Name or service not known') (opsiconfd|1517)
[2] [Nov 15 23:06:17]
(opsiconfd|1517)

the output of the ps aux | grep opsi:

ps aux | grep opsi
root 3184 0.0 0.4 3864 1192 tty2 S 20:34 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3211 0.0 0.4 3864 1188 tty2 S 20:35 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3238 0.0 0.4 3864 1188 tty2 S 20:35 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3273 0.0 0.4 3864 1192 tty2 S 20:36 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3342 0.0 0.4 3864 1192 tty2 S 20:36 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3355 0.0 0.4 3864 1192 tty2 S 20:36 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3359 0.0 0.4 3864 1192 tty2 S 20:36 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3388 0.0 0.4 3864 1188 tty2 S 20:37 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3452 0.0 0.4 3864 1192 tty2 S 20:37 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3465 0.0 0.4 3864 1188 tty2 S 20:37 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3469 0.0 0.4 3864 1192 tty2 S 20:37 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3518 0.0 0.4 3864 1188 tty2 S 20:37 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3528 0.0 0.4 3864 1192 tty2 S 20:37 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3588 0.0 0.4 3864 1188 tty2 S 20:37 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3592 0.0 0.4 3864 1188 tty2 S 20:37 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3605 0.0 0.4 3864 1192 tty2 S 20:37 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3657 0.0 0.4 3864 1192 tty2 S 20:38 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3713 0.0 0.4 3864 1188 tty2 S 20:38 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3718 0.0 0.4 3864 1188 tty2 S 20:38 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3737 0.0 0.4 3864 1192 tty2 S 20:38 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3859 0.0 0.4 3864 1188 tty2 S 20:38 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3868 0.0 0.4 3864 1192 tty2 S 20:38 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3915 0.0 0.4 3864 1188 tty2 S 20:38 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3923 0.0 0.4 3864 1192 tty2 S 20:38 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3935 0.0 0.4 3864 1192 tty2 S 20:38 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3947 0.0 0.4 3864 1192 tty2 S 20:38 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 3957 0.0 0.4 3864 1192 tty2 S 20:38 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 4007 0.0 0.4 3864 1176 tty2 S 20:39 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 4178 0.0 0.4 3864 1180 tty2 S 20:39 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 4198 0.0 0.4 3864 1184 tty2 S 20:39 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 4206 0.0 0.4 3864 1184 tty2 S 20:39 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 4212 0.0 0.4 3864 1184 tty2 S 20:39 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 4216 0.0 0.4 3864 1184 tty2 S 20:39 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 4221 0.0 0.4 3864 1180 tty2 S 20:39 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 4230 0.0 0.4 3864 1176 tty2 S 20:39 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 4261 0.0 0.4 3864 1180 tty2 S 20:39 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 4275 0.0 0.4 3864 1184 tty2 S 20:39 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 4285 0.0 0.4 3864 1180 tty2 S 20:39 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 4297 0.0 0.4 3864 1184 tty2 S 20:39 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 4300 0.0 0.4 3864 1176 tty2 S 20:39 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 4311 0.0 0.4 3864 1180 tty2 S 20:39 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 4317 0.0 0.4 3864 1176 tty2 S 20:39 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 4436 0.0 0.4 3864 1176 tty2 S 20:39 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 4477 0.0 0.4 3864 1180 tty2 S 20:39 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 4493 0.0 0.4 3864 1180 tty2 S 20:39 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 4498 0.0 0.4 3864 1180 tty2 S 20:39 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 4568 0.0 0.4 3872 1228 tty2 R 20:39 0:00 /bin/sh /etc/init.d/opsiconfd start
root 4580 0.0 0.4 3872 1228 tty2 S 20:39 0:00 /bin/sh /etc/init.d/opsiconfd start
root 4587 0.0 0.4 3872 1228 tty2 S 20:39 0:00 /bin/sh /etc/init.d/opsiconfd start
root 4590 0.0 0.4 3872 1228 tty2 R 20:39 0:00 /bin/sh /etc/init.d/opsiconfd start
993 4615 10.0 5.0 17292 12888 ? R 20:39 0:00 /usr/bin/python /usr/sbin/opsiconfd -D
root 4621 0.0 0.4 3864 1176 tty2 S 20:39 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
993 4629 6.0 4.8 16848 12384 ? S 20:39 0:00 /usr/bin/python /usr/sbin/opsiconfd -D
993 4632 2.0 4.7 16848 12276 ? S 20:39 0:00 /usr/bin/python /usr/sbin/opsiconfd -D
root 4635 0.0 0.4 3864 1184 tty2 S 20:39 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
993 4638 4.0 0.0 0 0 ? Rs 20:39 0:00 [opsiconfd]
993 4640 2.0 4.6 16848 11984 ? S 20:39 0:00 /usr/bin/python /usr/sbin/opsiconfd -D
993 4641 4.0 0.0 0 0 ? Rs 20:39 0:00 [opsiconfd]
993 4642 2.0 4.6 16848 11984 ? S 20:39 0:00 /usr/bin/python /usr/sbin/opsiconfd -D
993 4644 4.0 3.6 15360 9324 ? Rs 20:39 0:00 /usr/bin/python /usr/sbin/opsiconfd -D
993 4645 2.0 4.5 16852 11704 ? R 20:39 0:00 /usr/bin/python /usr/sbin/opsiconfd -D
root 4651 0.0 0.4 3864 1180 tty2 S 20:39 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 4659 0.0 0.1 3872 492 tty2 R 20:39 0:00 /bin/sh /etc/init.d/opsiconfd start
root 4661 0.0 0.0 0 0 tty2 Z 20:39 0:00 [opsiconfd] <defunct>
root 4663 0.0 0.4 3864 1176 tty2 S 20:39 0:00 /bin/sh +e /usr/sbin/opsiconfd-guard daemon
root 4666 0.0 0.1 3872 492 tty2 R 20:39 0:00 /bin/sh /etc/init.d/opsiconfd start
1000 4668 0.0 0.2 3116 716 pts/0 R+ 20:39 0:00 grep opsi
root 4670 0.0 0.1 3872 464 tty2 R 20:39 0:00 /bin/sh /etc/init.d/opsiconfd start
root 4672 0.0 0.4 3772 1052 tty2 R 20:39 0:00 su opsiconfd -c test -r /etc/shadow

first I thought the cause is network related, but the two server can see each other.
we hope you know what is the problem.

regards, np

Hello,

I ran into the same problem. After calling register-depot.py, the configed service came not up again (-2, 'Name or service not known'). I fixed that issue by installing opsi manually on a debian lenny installation, like described in the manual.

I had another error after calling register-depot.py on this installation again, which I cannot remember anymore. I fixed that by editing the /etc/hosts. I entered both depot servers on each servers /etc/hosts, after that it worked fine.

My servers were able to see each other on the network, too. But without the following insert into the /etc/hosts it did not work:
regards

Hi

all of my OPSI servers are manually installed Debian Lennys.
I hadn't any problem when I called the register-depot.py

hosts file (almost the defaults, I just added the required entries):

remotedepot:~# cat /etc/hosts
127.0.0.1 localhost
192.168.0.1 remotedepot.branchoffice.hu remotedepot
172.18.1.2 central.opsiserver.hu central

# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

regards, np

Does it work with this entries or still the same problem?
Maybe I had a different problem.

No idea anymore, sorry !

one last idea if it still does not work:

have you checked if the ports 4441, 4442 and 4447 are opened between the sites?

the hosts file was correct before the problem appeared. we allow only 4447 port between the two sites. where can I find instructions, what ports required for the correct functioning, and why it is important?

thanks for the helpful replies.

np

its mentioned in the opsi manual. the prelofinloaders is using 4441 to communicate with the config-server and 4442 for the notification server.
What I do not know if it would solve your problem to open this two ports. You have to try.

but we have no problems with the preloginloaders. the problem is around the depot server. anyway, i'll try your suggestion, and report the results.

np

how can I undo the depot server registration?

I figured out, that renaming the configuration files in /etc/opsi doesn't works.

np

allowing the two ports couldn't fix the problem.

np