Slow boot due to rpcbind services

[Andrew_adm]

Hi all,
After reboot a system customer noticed it wasn´t able to log in on it. Taking a look to syslog cu saw that along several minutes the system was loading loading rpcbind services from inetd.conf. We suggested comment rpc lines on inetd.conf file and it was resolved but they ask why it happens on this system and not on other similar system. As you can see in the log that follows recserv takes 10 minutes during the boot. i dont find the way to know what happens, can you help on this? :
Apr 10 16:33:57 geinueva su: + tty?? root-root
Apr 10 16:34:15 geinueva syslog: icapd: iCAP B.11.11.08.01.00.81 daemon starting
Apr 10 16:35:58 geinueva inetd[1078]: recserv/tcp: Added service, server /usr/lb
in/recserv
Apr 10 16:45:58 geinueva inetd[1078]: swat/tcp: Added service, server /opt/samba
/bin/swat
Apr 10 16:45:58 geinueva inetd[1078]: registrar/tcp: Added service

Thanks in advance.

[Rasheed Tamton]

Hi Andrew,

Check the global system file for recserv
/usr/lib/X11/app-defaults/RecServ and compare with your other systems where recserv running. The are some options which control the behavior of recserv like "AlwaysAsk" ,etc.

Do a man recserv for more info.

Regards,
Rasheed Tamton.

[Andrew_adm]

Hi Rasheed,
I took a look to this and all the systems i looked have the behaviour configured as AlwaysAsk so i dont think it be the cause.

[Rasheed Tamton]

#grep recs /etc/services

recserv 7815/tcp #
SharedX Receiver Service

Hope the port is ok.

Anything on /var/adm/inetd.sec which causes this.

Regards.

[Andrew_adm]

Port is ok in /etc/services and inetd.sec doesn´t exists on system. I thought create it and enable some systems on it but talking about an optional security file i decided not to do it.
Something in syslog calls my attention and it´s that recserv takes exactly 10 minutes, it makes me think about any delay, timeout, interval or something like this that could be configured in any conf file. Furthermore is not possible get connect to the system through telnet or rlogin during the boot until, i suppose, inetd load all services or, at least, recserv that i think is what causes the delay. Moreover, during the boot, out connections are done but not in-connections (rlogin, telnet,etc).

[Rasheed Tamton]

What I meant was that you do not have a firewall problem with the port.

Can you do these:
netstat -a|grep recs
netstat -an|grep 781

Also do you have this file on the said server:
/etc/vue/config/Xsession.d/0070.recs

Otherwise, if you can restart inetd with logging

inetd -l
and check the syslog.log

The last thing comes to my mind is the name service. Can you check that also.

[Andrew_adm]

doesn´t seem exist problem due to firewall, recserv appears as LISTEN and the port 7815 appears as LISTEN too, file 0070 exists and all places where appears the name of service looks fine. I have a doubt looking syslog, what is taking too much time? recserv or swat?. could it be recserv be added and swat takes 10 mins until is added??

[Rasheed Tamton · Accepted solution]

inetd -l
and check the syslog.log

How about samba/swat ports are they listening also.

See logs in /var/opt/samba/

[Andrew_adm]

Problem was solved. I have uncommented rpc lines in inetd.conf, enabled logging in inetd (inetd -l) and rebooted the system, it as up after ten minutes around.
Thank you very much Rasheed.

[Andrew_adm]

Problem was solved. I have uncommented rpc lines in inetd.conf, enabled logging in inetd (inetd -l) and rebooted the system, it was up after ten minutes around.
Thank you very much Rasheed.

[Andrew_adm]

Problem was solved. I have uncommented rpc lines in inetd.conf, enabled logging in inetd (inetd -l) and rebooted the system, it was up after ten minutes around and accepting connections.
Thank you very much Rasheed.

[Andrew_adm]

Solved.