Networker

Re: [Networker] BAckup error

2007-10-03 14:28:06
Subject: Re: [Networker] BAckup error
From: Tim Mooney <Tim.Mooney AT NDSU DOT EDU>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 3 Oct 2007 13:21:26 -0500
In regard to: Re: [Networker] BAckup error, Stan Sander said (at 8:50am on...:

On Wed, 2007-10-03 at 11:07 +0200, Elvis Ademba wrote:
Dear all

I get the following error, I have tried troubleshooting all i know i cant
fix it. it keep on coming back,

........................................................
10/03/07 11:01:45 savegrp: Client233:/ will retry 1 more time(s)
10/03/07 11:01:45 savegrp: Clientt233:/
started
save -s backupserver -g Daily_BCK -LL -f - -m Client233 -t 1190439327 -l 5
-W 78 -N / /
10/03/07 11:01:46 savegrp: job (171250) host: Client233 savepoint: / had
ERROR indication(s) at completion.
* Client233:/ 1 retry attempted
* Client233:/ save: SYSTEM error: client `localhost.localdomain' is not
properly configured on the NetWorker Server
* Client233:/ or `localhost.localdomain' is not in the aliases list for
client `Client233'
* Client233:/ save: Cannot open save session with backupserver
10/03/07 11:01:46 savegrp: Cleint233:/ failed.
................................................................

Regards
Elvis


I'll bet it's a Red Hat system and the client's hostname is on the same
line with the localhost entry in /etc/hosts.  Place the client's
hostname on it's own line with it's IP address.

That's pretty close to what I was going to guess.

I was also guessing it was a Red Hat client, but my guess was that the
hostname on the client was actually set to localhost.localdomain.  Elvis
could check that by logging in on the client and doing

        uname -n

If it is set to localhost.localdomain, then Elvis needs to update the
/etc/sysconfig/network file with the correct HOSTNAME setting.

PS: Elvis, providing the log message was good, but it's important
to give details about your environment when you're going to ask
questions on the list.  Especially when there are both clients and
servers involved, giving the details of both are important.  For a
question like this, you probably should also have provided:

- what the exact version of NetWorker is that you're running on the
  server.

- what operating system (e.g. Solaris, Windows) and version of the
  operating system you're running on the server (e.g. Solaris 10, Windows
  2003 Enterprise Server).

- it doesn't hurt to provide details about the hardware the server is on
  (e.g. Sun 420R with 4 400 MHz UltraSparc II processors and 4 GB RAM, or
  Dell PowerEdge 4444 server, two 3.0 GHZ dual-core Xeons with 2 GB RAM).

- you should provide all the same information for any client involved.
  Sometimes the problem is server-only, so you can skip that, but often
  there is a client involved, and if so, having the same information is
  helpful.

Tim
--
Tim Mooney                                        Tim.Mooney AT ndsu DOT edu
Information Technology Services                   (701) 231-1076 (Voice)
Room 242-J6, IACC Building                        (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the body of the email. Please write to networker-request 
AT listserv.temple DOT edu if you have any problems with this list. You can access the 
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

<Prev in Thread] Current Thread [Next in Thread>