Data Protector Practitioners Forum
Showing results for 
Search instead for 
Do you mean 

Lots of messages in logs like "xinetd EXIT omni status=0....;START omni status=0..."

Frequent Advisor

Lots of messages in logs like "xinetd EXIT omni status=0....;START omni status=0..."

Dears,

 

I saw many omni logs in system log file like belows. Is this right?

 

Apr 16 14:08:47 mbackup xinetd[8297]: EXIT: omni status=0 pid=15446 duration=0(sec)
Apr 16 14:08:50 mbackup xinetd[8297]: START: omni pid=15448 from=::ffff:
Apr 16 14:08:50 mbackup xinetd[8297]: EXIT: omni status=0 pid=15448 duration=0(sec)
Apr 16 14:08:50 mbackup xinetd[8297]: START: omni pid=15449 from=::ffff:
Apr 16 14:08:50 mbackup xinetd[8297]: EXIT: omni status=0 pid=15449 duration=0(sec)
Apr 16 14:08:50 mbackup xinetd[8297]: START: omni pid=15450 from=::ffff:
Apr 16 14:08:50 mbackup xinetd[8297]: EXIT: omni status=0 pid=15450 duration=0(sec)
Apr 16 14:08:50 mbackup xinetd[8297]: START: omni pid=15451 from=::ffff:
Apr 16 14:08:50 mbackup xinetd[8297]: EXIT: omni status=0 pid=15451 duration=0(sec)
Apr 16 14:08:53 mbackup kernel: program bma is using a deprecated SCSI ioctl, please convert it to SG_IO

3 REPLIES
Highlighted
Honored Contributor

Re: Lots of messages in logs like "xinetd EXIT omni status=0....;START omni status=0..."

That looks allright. You will see a log entry for each backup started from cell server on this client. xinetd is used to start the process for backup on the client.

 

Regards,

Sebastian

---
Please assign a KUDO to this post, if you find it useful.
Frequent Advisor

Re: Lots of messages in logs like "xinetd EXIT omni status=0....;START omni status=0..."

Hi Sebastian,

 

Thanks your quick reply. 

 

As you said, if a backup specification is started, there is one xinetd message in log file, right?

 

But I saw some log messages with the same IP address. Is this all right?

 

Thank you

Honored Contributor

Re: Lots of messages in logs like "xinetd EXIT omni status=0....;START omni status=0..."

When I remember correctly, a process is started per mount point on the client. Data Protector starts a disk agent based on concurrency/drive count in parallel.

Regards,
Sebastian
---
Please assign a KUDO to this post, if you find it useful.