ldcd error newfd = INVALID_SOCKET, newfd=-1, timersig=1, error=4, EINTR=4, selectret=-1
After upgrading from NetBackup 6.5.4 to 7.0 on Solaris X86 I'm seeing the following errors on /var/adm/messages:
Jan 24 10:38:50 beaker tldcd[1291]: [ID 101006 daemon.info] tldcd.c.2691, newfd = INVALID_SOCKET, newfd=-1, timersig=1, error=4, EINTR=4, selectret=-1
Jan 24 10:57:52 beaker tldcd[1291]: [ID 101006 daemon.info] tldcd.c.2691, newfd = INVALID_SOCKET, newfd=-1, timersig=1, error=4, EINTR=4, selectret=-1
Jan 24 11:15:18 beaker tldcd[1291]: [ID 101006 daemon.info] tldcd.c.2691, newfd = INVALID_SOCKET, newfd=-1, timersig=1, error=4, EINTR=4, selectret=-1
Jan 24 11:16:05 beaker tldcd[1291]: [ID 101006 daemon.info] tldcd.c.2691, newfd = INVALID_SOCKET, newfd=-1, timersig=1, error=4, EINTR=4, selectret=-1
Jan 24 12:26:07 beaker tldcd[1291]: [ID 101006 daemon.info] tldcd.c.2691, newfd = INVALID_SOCKET, newfd=-1, timersig=1, error=4, EINTR=4, selectret=-1
Jan 24 12:42:56 beaker tldcd[1291]: [ID 101006 daemon.info] tldcd.c.2691, newfd = INVALID_SOCKET, newfd=-1, timersig=1, error=4, EINTR=4, selectret=-1
Jan 24 12:43:29 beaker tldcd[1291]: [ID 101006 daemon.info] tldcd.c.2691, newfd = INVALID_SOCKET, newfd=-1, timersig=1, error=4, EINTR=4, selectret=-1
Jan 24 12:44:28 beaker tldcd[1291]: [ID 101006 daemon.info] tldcd.c.2691, newfd = INVALID_SOCKET, newfd=-1, timersig=1, error=4, EINTR=4, selectret=-1
The MOSC folks throught maybe this form could help.
Thanks for any clues,
Glen
Comments
I think you can ignore them?
They're logged at "info" level.
Is there any context? Do you have any messages surrounding it at "notice" or higher severity? Perhaps something from tldd, if not tldcd?
Anything interesting in the bptm log around the same time?
This IS Solaris 10 x64, right? I think that's the only Solaris x86 NetBackup 7.0 is supported on as a server...
What debugging have you set up for the media manager? Check /usr/openv/volmgr/debug and see if you have "VERBOSE" in /usr/openv/volmgr/vm.conf. (If you do, do you still need it/them?)
Chris, I think this is a
Chris,
I think this is a complete set - at least timestamp wise:
Jan 21 05:28:22 beaker ltid[12651]: [ID 560358 daemon.notice] LTID - Sent ROBOTIC request, Type=3, Param2=1
Jan 21 05:28:22 beaker tldd[12703]: [ID 145620 daemon.notice] TLD(0) DismountTape 4100L4 from drive 2
Jan 21 05:28:51 beaker tldcd[12734]: [ID 438312 daemon.info] tldcd.c.3062, process_request(), received command=3, from peername=beaker, version 50
Jan 21 05:28:51 beaker tldcd[12734]: [ID 282422 daemon.notice] Processing UNMOUNT, TLD(0) drive 2, slot 31, barcode 004100L4 , vsn 4100L4
Jan 21 05:28:51 beaker tldcd[7249]: [ID 329091 daemon.notice] TLD(0) opening robotic path /dev/sg/c0tw500110a0008ca5dal1
Jan 21 05:28:51 beaker tldcd[7249]: [ID 640195 daemon.notice] inquiry() function processing library HP MSL G3 Series G.20:
Jan 21 05:28:51 beaker tldcd[7249]: [ID 219741 daemon.notice] TLD(0) initiating MOVE_MEDIUM from addr 2 to addr 1031
Jan 21 05:29:14 beaker tldcd[7249]: [ID 559680 daemon.notice] TLD(0) closing/unlocking robotic path
Jan 21 05:29:14 beaker tldcd[12734]: [ID 640195 daemon.notice] inquiry() function processing library HP MSL G3 Series G.20:
Jan 21 05:29:14 beaker tldcd[12734]: [ID 101006 daemon.info] tldcd.c.2691, newfd = INVALID_SOCKET, newfd=-1, timersig=1, error=4, EINTR=4, selectret=-1
Jan 21 05:29:14 beaker tldd[12703]: [ID 858910 daemon.notice] DecodeDismount: TLD(0) drive 2, Actual status: STATUS_SUCCESS
I'll check the logs but I think I lost the log settings that I had made to 6.5.4 during the upgrade.
Thanks for the help,
Glen
[added w/edit] - yes the server is Solaris x86_64 - it's a Sun X4500 - two double core AMD CPUs.
I really think that's just an
I really think that's just an information message you can safely ignore. If it's bugging somebody you can change syslog.conf to only log at "notice" and above and discard "info" severity messages.
(This is where everyone else has a chance to tell me I'm totally wrong
)
I think pursuing this further will involve checking what debugging you have/have not set up along with the bptm logs, as I mentioned in my earlier post.
Would you like to reply?
Login or Register to post your comment.