Error 233: premature eof encountered

[Dreamleo]

Hi

Need some help on this issue.

I just upgraded one Netbackup master server from 5.1MP4 to 6.5.3, it's running on Windows 2003. After that the backup jobs randomly failed with error 233. The job may fail yesterday then successful today, it's not related to the OS, client version and start time.

I checked the bpbrm log, it shows something like

20:06:02.281 [8060.5696] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2043: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
20:06:02.281 [8060.5696] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2057: service: bpdbm
20:06:02.281 [8060.5696] <2> logconnections: BPDBM CONNECT FROM 192.168.80.34.2188 TO 192.168.80.34.13724
20:06:02.687 [8060.5696] <2> get_long: (2) premature end of file (byte 1)
20:06:02.687 [8060.5696] <2> db_getdata: get_string() failed: Access is denied. (5) premature end of file encountered (-9)
20:06:02.687 [8060.5696] <2> db_end_sts: no DONE from db_getreply(): premature eof encountered
20:06:02.703 [8060.5696] <16> bpbrm handle_backup: db_FLISTsend failed: premature eof encountered (233)

Anyone had the same problem before? Any suggestion is really appreciated.

Thanks

Leo

[J_H_Is_gone]

I beg you please, please, open a case with support.

I have been getting 233's for about 1 1/2 years. 

Funny thing is I only get them on my unix servers.  while you get them on a windows server.

I only get them on file systems that have been samba-ed out like /home.

And just like you, I may get a 0 return for weeks, then get a 233 for 1 or even 2 nights, then go back to getting 0's.

I opened my first support ticket 8/28/2008

Worked on it for quite a while - has been pushed up to where I have a designated rep working on it.

Every time I get a 233 I send it to him, telling him what server and what directory (like I said always my unix servers and always a dir that has been samba-ed out).

We have looked at logs, tried to look at file lists to see if they are different, to see what file is new today that was not there yesterday.

Please open the call, maybe your windows issues will give them some extra clues that my issue has not brought to light.

As far as I know, no one else has reported the 233 errors.

[Anth105]

Hi

I have  the same problem described as per  Leo  except I am encountering it on the NAS clients  ( NDMP backup )  Full backups only.  No issue what sort ever on the  INCR's.

Here is an excerpt of the bpbrm log:

18/04/2009 11:58:39 - started process bpbrm (2232)
18/04/2009 11:58:40 - connecting
18/04/2009 11:58:40 - connected; connect time: 00:00:00
18/04/2009 11:58:44 - mounting A00687
18/04/2009 11:59:06 - mounted; mount time: 00:00:22
18/04/2009 11:59:07 - positioning A00687 to file 69
18/04/2009 12:00:08 - positioned A00687; position time: 00:01:01
18/04/2009 12:00:08 - begin writing
18/04/2009 14:28:10 - Error bpbrm(pid=2232) db_FLISTsend failed: premature eof encountered (233)
18/04/2009 14:28:12 - Error ndmpagent(pid=3044) terminated by parent process
18/04/2009 14:28:13 - Error ndmpagent(pid=3044) NDMP backup failed, path = /esp34/esp34
18/04/2009 14:28:33 - Error ndmpagent(pid=3044) NDMP_LOG_ERROR 0 Medium error
18/04/2009 14:28:34 - Error ndmpagent(pid=3044) NDMP_LOG_ERROR 0 Backup is aborted.
18/04/2009 14:29:01 - end writing; write time: 02:28:53
premature eof encountered(233)


Any help will be much appreciated.

Anthony

[Pravs]

your problem appear to be same as described in ET (internal Bug report) 1525631 reported for 6.5.4. i think, you shoul call support with bptm, bpdbm logs.
JFYI, we are also working with Microsoft on this issue.

[Pravs]

I just researched on your case as well. Seems it's the same problem as DreamLeo facing though you are seeing it for NDMP Backups.

are you getting this error at end for your NDMP backup? "the file list is incomplete(249)".

are you getting different failure status at random? is it failing intermittently or always?

A study of bpbrm, bptm and bpdbm logs will be helpful. fro my eyes, it's same issue as 1st post.

[Pravs]

you may wish to pass your case no. as well. so that it will be useful for others to see if they are hitting the same error.

[Anth105]

Hi Pravs,

The full scheduled backup jobs randomly  and intermittently  fail  with error 233 and run succesfully when I manually start them.

FYI: Master server is running on AIX 5.3 and the media server is on W2K

I will collect the bpbrm, bptm and bpdbm logs  and open a support call for further investigation.

many thanks for your help


Anth


 

[Anth105]

Hi Pravs,

The full scheduled backup jobs randomly  and intermittently  fail  with error 233 and run succesfully when I manually start them.

FYI: Master server is running on AIX 5.3 and the media server is on W2K

I will collect the bpbrm, bptm and bpdbm logs  and open a support call for further investigation.

many thanks for your help


Anth


 

[J_H_Is_gone]

FYI - I ONLY get it on AIX clients ( never got it on a windows client)

some of my issue number are old as I have been working on this for over a year.

291-059-997
220-422-448
281-369-029
220-592-500 ( current ticket)

[Pravs]

Ok. That's good. I could not get enough time to go through all the case notes. perhaps you can ask the support to review ET 1525631 and other related ETs (duplicated, referenced in the same ET). I am not sure if it's same problem but it may give some hint to the support person who is researching your case.

[Pravs]

guys, how the things going on ?

[J_H_Is_gone]

We seem to be a bit closer and are waiting for the next failure.  We think this time we will get some good info in the logs they are asking for.