Problem Report - Veritas Net Backup

This is a discussion on Problem Report - Veritas Net Backup ; Has anyone else seen these messages in the problem report: 18/04/2000 11:55:15 sn00 Critical get_string() failed - incoming data too large for buffer (0) bprd 18/04/2000 11:55:15 sn00 Critical could not process request from sn00 bprd These occur every 5 ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: Problem Report

  1. Problem Report


    Has anyone else seen these messages in the problem report:

    18/04/2000 11:55:15 sn00 Critical get_string() failed - incoming data too
    large for buffer (0) bprd
    18/04/2000 11:55:15 sn00 Critical could not process request from sn00 bprd

    These occur every 5 minutes but do not seem to affect performance in any
    way.

    Dave.


  2. Re: Problem Report


    Well, I take a shot at this...

    No I have never seen that message before, but have made any changes recently
    to you NBU master / media server? Is this a master or media server? Have
    you created /usr/openv/netbackup/logs/bprd to see what additional information
    can be logged?

    I'd also suggest putting VERBOSE in your server's bp.conf file prior to creating
    the log directory.

    -David Chapa
    DataStaff, Inc.

    "dave pearson" wrote:
    >
    >Has anyone else seen these messages in the problem report:
    >
    >18/04/2000 11:55:15 sn00 Critical get_string() failed - incoming data too
    >large for buffer (0) bprd
    >18/04/2000 11:55:15 sn00 Critical could not process request from sn00 bprd
    >
    >These occur every 5 minutes but do not seem to affect performance in any
    >way.
    >
    >Dave.
    >



  3. Re: Problem Report


    David,

    This is what's in the bprd log on the master server (which is also a media
    server):

    00:15:26 [19075] <4> connected_peer: Connection from host sn00, 164.48.216.100,
    on non-reserved port 52154
    00:15:26 [19075] <16> get_string: buffer space for 3072 bytes, but incoming
    data
    needs 1903520116 bytes
    00:15:26 [19075] <16> get_string: (7) inadequate buffer space for data
    00:15:26 [19075] <2> getsockconnected: host=sn00 service=bpdbm address=164.48.21
    6.100 protocol=tcp non-reserved port=13721
    00:15:26 [19075] <32> process_request: get_string() failed - incoming data
    too l
    arge for buffer (0)
    00:15:26 [19075] <2> getsockconnected: host=sn00 service=bpdbm address=164.48.21
    6.100 protocol=tcp non-reserved port=13721
    00:15:26 [19075] <32> process_request: could not process request from sn00


    I'll see if the VERBOSE setting tells us any more.

    Dave.


    "David Chapa" wrote:
    >
    >Well, I take a shot at this...
    >
    >No I have never seen that message before, but have made any changes recently
    >to you NBU master / media server? Is this a master or media server? Have
    >you created /usr/openv/netbackup/logs/bprd to see what additional information
    >can be logged?
    >
    >I'd also suggest putting VERBOSE in your server's bp.conf file prior to

    creating
    >the log directory.
    >
    >-David Chapa
    >DataStaff, Inc.
    >
    >"dave pearson" wrote:
    >>
    >>Has anyone else seen these messages in the problem report:
    >>
    >>18/04/2000 11:55:15 sn00 Critical get_string() failed - incoming data

    too
    >>large for buffer (0) bprd
    >>18/04/2000 11:55:15 sn00 Critical could not process request from sn00

    bprd
    >>
    >>These occur every 5 minutes but do not seem to affect performance in any
    >>way.
    >>
    >>Dave.
    >>

    >



  4. Re: Problem Report


    Well, after looking at this I would also create the bpdbm directory log.
    Also are you on Solaris?

    NOTE: WHEN YOU CREATE THE BPDBM LOGGING DIRECTORY, YOU MUST KEEP IN MIND
    THAT THIS IS ACTIVE LOGGING AND DOES NOT TERMINATE WHEN YOU DELETE THE DIRECTORY
    (THE DIRECTORY WILL BE RE-CREATED BY BPDBM SHOULD YOU DELETE IT WITHOUT GOING
    THROUGH THE PROPER STEPS). IT WILL GET LARGE. THEREFORE IT IS VERY IMPORTANT
    THAT YOU FOLLOW THESE INSTRUCTIONS FOR REMOVING/MOVING THE LOG DIRECTORY.

    bpdbm -terminate <>

    then either move or remove the bpdbm logging directory

    initbpdbm <>

    make sure that a new bpdbm logging directory has not been re-created.


    "Dave Pearson" wrote:
    >
    >David,
    >
    >This is what's in the bprd log on the master server (which is also a media
    >server):
    >
    >00:15:26 [19075] <4> connected_peer: Connection from host sn00, 164.48.216.100,
    >on non-reserved port 52154
    >00:15:26 [19075] <16> get_string: buffer space for 3072 bytes, but incoming
    >data
    > needs 1903520116 bytes
    >00:15:26 [19075] <16> get_string: (7) inadequate buffer space for data
    >00:15:26 [19075] <2> getsockconnected: host=sn00 service=bpdbm address=164.48.21
    >6.100 protocol=tcp non-reserved port=13721
    >00:15:26 [19075] <32> process_request: get_string() failed - incoming data
    >too l
    >arge for buffer (0)
    >00:15:26 [19075] <2> getsockconnected: host=sn00 service=bpdbm address=164.48.21
    >6.100 protocol=tcp non-reserved port=13721
    >00:15:26 [19075] <32> process_request: could not process request from sn00
    >
    >
    >I'll see if the VERBOSE setting tells us any more.
    >
    >Dave.
    >
    >
    >"David Chapa" wrote:
    >>
    >>Well, I take a shot at this...
    >>
    >>No I have never seen that message before, but have made any changes recently
    >>to you NBU master / media server? Is this a master or media server? Have
    >>you created /usr/openv/netbackup/logs/bprd to see what additional information
    >>can be logged?
    >>
    >>I'd also suggest putting VERBOSE in your server's bp.conf file prior to

    >creating
    >>the log directory.
    >>
    >>-David Chapa
    >>DataStaff, Inc.
    >>
    >>"dave pearson" wrote:
    >>>
    >>>Has anyone else seen these messages in the problem report:
    >>>
    >>>18/04/2000 11:55:15 sn00 Critical get_string() failed - incoming data

    >too
    >>>large for buffer (0) bprd
    >>>18/04/2000 11:55:15 sn00 Critical could not process request from sn00

    >bprd
    >>>
    >>>These occur every 5 minutes but do not seem to affect performance in any
    >>>way.
    >>>
    >>>Dave.
    >>>

    >>

    >



  5. Re: Problem Report


    David,

    Here are the bpdbm log entries:

    00:15:26 [19077] <4> connected_peer: Connection from host sn00, 164.48.216.100,
    on non-reserved port 52155
    00:15:26 [19081] <4> bpdbm: exiting because another daemon is running
    00:15:26 [19077] <2> error_db: Q_ERRADD
    00:15:26 [19077] <4> bpdbm: request complete: exit status 0
    00:15:26 [19082] <4> connected_peer: Connection from host sn00, 164.48.216.100,
    on non-reserved port 52156
    00:15:26 [19082] <2> error_db: Q_ERRADD
    00:15:26 [19082] <4> bpdbm: request complete: exit status 0
    00:15:28 [19093] <4> connected_peer: Connection from host sn00, 164.48.216.100,
    on non-reserved port 52157
    00:15:28 [19093] <16> get_string: buffer space for 40 bytes, but incoming
    data n
    eeds 1903520116 bytes
    00:15:28 [19093] <16> get_string: (7) inadequate buffer space for data
    00:15:28 [19093] <16> db_getdata: get_string() failed: Error 0 (0) incoming
    data
    too large for buffer (-1)
    00:15:28 [19093] <16> process_request: db_getrequest() failed: inadequate
    buffer
    space
    00:15:28 [19093] <4> bpdbm: request complete: exit status 235 inadequate
    buffer
    space
    Good luck!

    Dave.

    "David Chapa" wrote:
    >
    >Well, after looking at this I would also create the bpdbm directory log.


    >Also are you on Solaris?
    >
    >NOTE: WHEN YOU CREATE THE BPDBM LOGGING DIRECTORY, YOU MUST KEEP IN MIND
    >THAT THIS IS ACTIVE LOGGING AND DOES NOT TERMINATE WHEN YOU DELETE THE DIRECTORY
    >(THE DIRECTORY WILL BE RE-CREATED BY BPDBM SHOULD YOU DELETE IT WITHOUT

    GOING
    >THROUGH THE PROPER STEPS). IT WILL GET LARGE. THEREFORE IT IS VERY IMPORTANT
    >THAT YOU FOLLOW THESE INSTRUCTIONS FOR REMOVING/MOVING THE LOG DIRECTORY.
    >
    >bpdbm -terminate <>
    >
    >then either move or remove the bpdbm logging directory
    >
    >initbpdbm <>
    >
    >make sure that a new bpdbm logging directory has not been re-created.
    >
    >
    >"Dave Pearson" wrote:
    >>
    >>David,
    >>
    >>This is what's in the bprd log on the master server (which is also a media
    >>server):
    >>
    >>00:15:26 [19075] <4> connected_peer: Connection from host sn00, 164.48.216.100,
    >>on non-reserved port 52154
    >>00:15:26 [19075] <16> get_string: buffer space for 3072 bytes, but incoming
    >>data
    >> needs 1903520116 bytes
    >>00:15:26 [19075] <16> get_string: (7) inadequate buffer space for data
    >>00:15:26 [19075] <2> getsockconnected: host=sn00 service=bpdbm address=164.48.21
    >>6.100 protocol=tcp non-reserved port=13721
    >>00:15:26 [19075] <32> process_request: get_string() failed - incoming data
    >>too l
    >>arge for buffer (0)
    >>00:15:26 [19075] <2> getsockconnected: host=sn00 service=bpdbm address=164.48.21
    >>6.100 protocol=tcp non-reserved port=13721
    >>00:15:26 [19075] <32> process_request: could not process request from sn00
    >>
    >>
    >>I'll see if the VERBOSE setting tells us any more.
    >>
    >>Dave.
    >>
    >>
    >>"David Chapa" wrote:
    >>>
    >>>Well, I take a shot at this...
    >>>
    >>>No I have never seen that message before, but have made any changes recently
    >>>to you NBU master / media server? Is this a master or media server?

    Have
    >>>you created /usr/openv/netbackup/logs/bprd to see what additional information
    >>>can be logged?
    >>>
    >>>I'd also suggest putting VERBOSE in your server's bp.conf file prior to

    >>creating
    >>>the log directory.
    >>>
    >>>-David Chapa
    >>>DataStaff, Inc.
    >>>
    >>>"dave pearson" wrote:
    >>>>
    >>>>Has anyone else seen these messages in the problem report:
    >>>>
    >>>>18/04/2000 11:55:15 sn00 Critical get_string() failed - incoming data

    >>too
    >>>>large for buffer (0) bprd
    >>>>18/04/2000 11:55:15 sn00 Critical could not process request from sn00

    >>bprd
    >>>>
    >>>>These occur every 5 minutes but do not seem to affect performance in

    any
    >>>>way.
    >>>>
    >>>>Dave.
    >>>>
    >>>

    >>

    >



  6. Re: Problem Report


    Dave:

    The status code of 235 which was in your bpdbm log is explained in the Troubleshooting
    Guide, page 138.

    This usually means that there is a mismatch between server and client software
    versions.

    Good Luck!

    David Chapa
    DataStaff, Inc.

    "Dave Pearson" wrote:
    >
    >David,
    >
    >Here are the bpdbm log entries:
    >
    >00:15:26 [19077] <4> connected_peer: Connection from host sn00, 164.48.216.100,
    >on non-reserved port 52155
    >00:15:26 [19081] <4> bpdbm: exiting because another daemon is running
    >00:15:26 [19077] <2> error_db: Q_ERRADD
    >00:15:26 [19077] <4> bpdbm: request complete: exit status 0
    >00:15:26 [19082] <4> connected_peer: Connection from host sn00, 164.48.216.100,
    >on non-reserved port 52156
    >00:15:26 [19082] <2> error_db: Q_ERRADD
    >00:15:26 [19082] <4> bpdbm: request complete: exit status 0
    >00:15:28 [19093] <4> connected_peer: Connection from host sn00, 164.48.216.100,
    >on non-reserved port 52157
    >00:15:28 [19093] <16> get_string: buffer space for 40 bytes, but incoming
    >data n
    >eeds 1903520116 bytes
    >00:15:28 [19093] <16> get_string: (7) inadequate buffer space for data
    >00:15:28 [19093] <16> db_getdata: get_string() failed: Error 0 (0) incoming
    >data
    > too large for buffer (-1)
    >00:15:28 [19093] <16> process_request: db_getrequest() failed: inadequate
    >buffer
    > space
    >00:15:28 [19093] <4> bpdbm: request complete: exit status 235 inadequate
    >buffer
    >space
    >Good luck!
    >
    >Dave.
    >
    >"David Chapa" wrote:
    >>
    >>Well, after looking at this I would also create the bpdbm directory log.

    >
    >>Also are you on Solaris?
    >>
    >>NOTE: WHEN YOU CREATE THE BPDBM LOGGING DIRECTORY, YOU MUST KEEP IN MIND
    >>THAT THIS IS ACTIVE LOGGING AND DOES NOT TERMINATE WHEN YOU DELETE THE

    DIRECTORY
    >>(THE DIRECTORY WILL BE RE-CREATED BY BPDBM SHOULD YOU DELETE IT WITHOUT

    >GOING
    >>THROUGH THE PROPER STEPS). IT WILL GET LARGE. THEREFORE IT IS VERY IMPORTANT
    >>THAT YOU FOLLOW THESE INSTRUCTIONS FOR REMOVING/MOVING THE LOG DIRECTORY.
    >>
    >>bpdbm -terminate <>
    >>
    >>then either move or remove the bpdbm logging directory
    >>
    >>initbpdbm <>
    >>
    >>make sure that a new bpdbm logging directory has not been re-created.
    >>
    >>
    >>"Dave Pearson" wrote:
    >>>
    >>>David,
    >>>
    >>>This is what's in the bprd log on the master server (which is also a media
    >>>server):
    >>>
    >>>00:15:26 [19075] <4> connected_peer: Connection from host sn00, 164.48.216.100,
    >>>on non-reserved port 52154
    >>>00:15:26 [19075] <16> get_string: buffer space for 3072 bytes, but incoming
    >>>data
    >>> needs 1903520116 bytes
    >>>00:15:26 [19075] <16> get_string: (7) inadequate buffer space for data
    >>>00:15:26 [19075] <2> getsockconnected: host=sn00 service=bpdbm address=164.48.21
    >>>6.100 protocol=tcp non-reserved port=13721
    >>>00:15:26 [19075] <32> process_request: get_string() failed - incoming

    data
    >>>too l
    >>>arge for buffer (0)
    >>>00:15:26 [19075] <2> getsockconnected: host=sn00 service=bpdbm address=164.48.21
    >>>6.100 protocol=tcp non-reserved port=13721
    >>>00:15:26 [19075] <32> process_request: could not process request from

    sn00
    >>>
    >>>
    >>>I'll see if the VERBOSE setting tells us any more.
    >>>
    >>>Dave.
    >>>
    >>>
    >>>"David Chapa" wrote:
    >>>>
    >>>>Well, I take a shot at this...
    >>>>
    >>>>No I have never seen that message before, but have made any changes recently
    >>>>to you NBU master / media server? Is this a master or media server?


    >Have
    >>>>you created /usr/openv/netbackup/logs/bprd to see what additional information
    >>>>can be logged?
    >>>>
    >>>>I'd also suggest putting VERBOSE in your server's bp.conf file prior

    to
    >>>creating
    >>>>the log directory.
    >>>>
    >>>>-David Chapa
    >>>>DataStaff, Inc.
    >>>>
    >>>>"dave pearson" wrote:
    >>>>>
    >>>>>Has anyone else seen these messages in the problem report:
    >>>>>
    >>>>>18/04/2000 11:55:15 sn00 Critical get_string() failed - incoming data
    >>>too
    >>>>>large for buffer (0) bprd
    >>>>>18/04/2000 11:55:15 sn00 Critical could not process request from sn00
    >>>bprd
    >>>>>
    >>>>>These occur every 5 minutes but do not seem to affect performance in

    >any
    >>>>>way.
    >>>>>
    >>>>>Dave.
    >>>>>
    >>>>
    >>>

    >>

    >



+ Reply to Thread