Re: new linux client install
Stefan G. Weichinger wrote: Paul Bijnens schrieb: I think I see the light... :-) The /tmp/amanda directory is owned by the wrong user! or is not writable by the amanda-user, yes ... I saw that light also ;-) Let's see if it gets through now ... Stefan OK, yes it did get rather confusing, apologies! But thanks to all for the help, it appears that it was indeed the ownership of /tmp/amanda that was causing the problem as my amcheck doesn't complain anymore! Its certainly been a learning experience!! Much thanks, John
Re: new linux client install
Pavel Pragin wrote: John Clement wrote: Having read through some of the documentation it seemed a fairly straight forward thing to install an Amanda client. However, I used an rpm for it, having been forced to upgrade my tar software too but it appears to be running as amandabackup and in /var/lib... So I'm now getting the following: amandad: time 0.002: accept error: access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: Permission denied amandad: time 0.002: sending NAK pkt: ERROR access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: Permission denied at the bottom of my amcheck. I've confirmed that the file is owned and chmoded correctly: -rw--- 1 amandabackup disk 109 Apr 25 14:23 .amandahosts If I change the ownership or permissions it complains, so I think they are correct. In the .amandahosts file I have server.domain.tld amanda server amanda server.domain.tld amandabackup #added incase it made a difference server amandabackup #added incase it made a difference So can anyone make any suggestions? Thanks make sure that /var/lib/amanda/.amandahosts is owned by amanda and the group is set to disk chown amanda:disk /var/lib/amanda/.amandahosts Sorry, yes, it was infact owned by amanda:disk, the line I posted was from one of the 'lets just change something and hope it works' attempts I was having...
Re: new linux client install
Paul Bijnens wrote:
On 2006-04-26 10:12, John Clement wrote:
Pavel Pragin wrote:
John Clement wrote:
Having read through some of the documentation it seemed a fairly
straight forward thing to install an Amanda client. However, I
used an rpm for it, having been forced to upgrade my tar software
too but it appears to be running as amandabackup and in
/var/lib... So I'm now getting the following:
amandad: time 0.002: accept error: access as amandabackup not
allowed from [EMAIL PROTECTED]: cannot open
/var/lib/amanda/.amandahosts: Permission denied
amandad: time 0.002: sending NAK pkt:
ERROR access as amandabackup not allowed from [EMAIL PROTECTED]:
cannot open /var/lib/amanda/.amandahosts: Permission denied
at the bottom of my amcheck. I've confirmed that the file is owned
and chmoded correctly:
-rw--- 1 amandabackup disk 109 Apr 25 14:23 .amandahosts
If I change the ownership or permissions it complains, so I think
they are correct. In the .amandahosts file I have
server.domain.tld amanda
server amanda
server.domain.tld amandabackup #added incase it made a difference
server amandabackup #added incase it made a difference
So can anyone make any suggestions?
Thanks
make sure that /var/lib/amanda/.amandahosts is owned by amanda and
the group is set to disk chown amanda:disk
/var/lib/amanda/.amandahosts
Sorry, yes, it was infact owned by amanda:disk, the line I posted was
from one of the 'lets just change something and hope it works'
attempts I was having...
...
It should be owned by the user the runs the amanda software.
It seems that is amandabackup in your setup.
Anatomy of the errormsg:
access as amandabackup not allowed
from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts:
Permission denied
amandabackup is the local user
[EMAIL PROTECTED] is the [EMAIL PROTECTED] that tries to connect.
And the errormsg is that the local user amandabackup has no
permission to read/access the file .amandahosts .
So try:
# su amandabackup -c cat /var/lib/amanda/.amandahosts
and fix those permissions.
OK, the story continues, thanks to all those who've contributed so
far!! Here's how things are now after all your comments. The client is
a new install of 2.5, server is 2.4.4p3
-rw--- 1 amandabackup disk 109 Apr 25 14:23 .amandahosts
/, /var, /lib, /var/lib/amanda are all readable.
xinetd.d/amanda:
=
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= amandabackup
group = disk
groups = yes
server = /usr/lib/amanda/amandad
disable = no
only_from = 10.10.1.8 192.168.0.1
}
=
but still I get this from amcheck:
ERROR: NAK murray.deanst.rroom.net: access as amandabackup not allowed
from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts:
Permission denied
Any more suggestions? - thanks
Re: new linux client install
John Clement schrieb:
OK, the story continues, thanks to all those who've contributed so
far!! Here's how things are now after all your comments. The client is
a new install of 2.5, server is 2.4.4p3
-rw--- 1 amandabackup disk 109 Apr 25 14:23 .amandahosts
/, /var, /lib, /var/lib/amanda are all readable.
xinetd.d/amanda:
=
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= amandabackup
group = disk
groups = yes
server = /usr/lib/amanda/amandad
disable = no
only_from = 10.10.1.8 192.168.0.1
}
=
but still I get this from amcheck:
ERROR: NAK murray.deanst.rroom.net: access as amandabackup not allowed
from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts:
Permission denied
Any more suggestions? - thanks
Was xinetd restarted after editing that file?
What if you remove the only_from-line for a test (and restart xinetd)?
Here it looks like
# ls -la ~amanda/.amandahosts
-rw--- 1 amanda root 190 Jun 27 2005 /var/lib/amanda/.amandahosts
Stefan
Re: new linux client install
On 2006-04-26 11:17, John Clement wrote: ERROR: NAK murray.deanst.rroom.net: access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: Permission denied Any more suggestions? - thanks What about leaving the Amanda set up alone for while, and just trying just this: # su amandabackup -c cat /var/lib/amanda/.amandahosts Does that work, or do you get Permission denied? -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: new linux client install
Paul Bijnens wrote: On 2006-04-26 11:17, John Clement wrote: ERROR: NAK murray.deanst.rroom.net: access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: Permission denied Any more suggestions? - thanks What about leaving the Amanda set up alone for while, and just trying just this: # su amandabackup -c cat /var/lib/amanda/.amandahosts Does that work, or do you get Permission denied? Hey Paul, sorry I didn't think to include the result of doing this earlier: [EMAIL PROTECTED] amanda]# su amandabackup -c cat /var/lib/amanda/.amandahosts orinoco.deanst.rroom.netamanda orinoco amanda [EMAIL PROTECTED] amanda]# thanks
Re: new linux client install
On 2006-04-26 12:03, John Clement wrote: -rw--- 1 amandabackup disk 109 Apr 25 14:23 .amandahosts /, /var, /lib, /var/lib/amanda are all readable. To be complete, they should also be executable. Oh yea, restarting xinetd, probably a good idea! Output from amcheck now: WARNING: murray.deanst.rroom.net: selfcheck request timed out. Host down? Now it looks like xinetd had some problem with it. Is there something listening on port 10080/udp? Is there a debugfile created (/tmp/amanda/amandad.*.debug)? What is in it? -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: new linux client install
Paul Bijnens wrote: On 2006-04-26 12:03, John Clement wrote: -rw--- 1 amandabackup disk 109 Apr 25 14:23 .amandahosts /, /var, /lib, /var/lib/amanda are all readable. To be complete, they should also be executable. Just made that change. Oh yea, restarting xinetd, probably a good idea! Output from amcheck now: WARNING: murray.deanst.rroom.net: selfcheck request timed out. Host down? Now it looks like xinetd had some problem with it. Is there something listening on port 10080/udp? Is there a debugfile created (/tmp/amanda/amandad.*.debug)? What is in it? Since changing the user in xinetd to 'amandabackup' there haven't been any debug files. I checked by putting 'amanda' back in there and restarting xinetd and I did get another debug file, complaining that access as amandabackup is not allowed from [EMAIL PROTECTED] jc
Re: new linux client install
Paul Bijnens wrote: On 2006-04-26 12:03, John Clement wrote: -rw--- 1 amandabackup disk 109 Apr 25 14:23 .amandahosts /, /var, /lib, /var/lib/amanda are all readable. To be complete, they should also be executable. Just made that change. Oh yea, restarting xinetd, probably a good idea! Output from amcheck now: WARNING: murray.deanst.rroom.net: selfcheck request timed out. Host down? Now it looks like xinetd had some problem with it. Is there something listening on port 10080/udp? Is there a debugfile created (/tmp/amanda/amandad.*.debug)? What is in it? Since changing the user in xinetd to 'amandabackup' there haven't been any debug files. I checked by putting 'amanda' back in there and restarting xinetd and I did get another debug file, complaining that access as amandabackup is not allowed from [EMAIL PROTECTED] jc
Re: new linux client install
John Clement schrieb: Paul Bijnens wrote: Is there a debugfile created (/tmp/amanda/amandad.*.debug)? What is in it? Since changing the user in xinetd to 'amandabackup' there haven't been any debug files. I checked by putting 'amanda' back in there and restarting xinetd and I did get another debug file, complaining that access as amandabackup is not allowed from [EMAIL PROTECTED] amanad? Third variation now ... check for typos in there. If ok, show us .amandahosts AND Output of amcheck again. -- Decide for one user, amanda OR amandabackup. What user did you configure/compile Amanda with? Make sure that user exists on that system, add it to the disk-group. Stefan
Re: new linux client install
On 2006-04-26 15:59, John Clement wrote: Paul Bijnens wrote: On 2006-04-26 12:03, John Clement wrote: /, /var, /lib, /var/lib/amanda are all readable. To be complete, they should also be executable. Just made that change. Do you mean that one of the directories were not executable before, but now is? Oh yea, restarting xinetd, probably a good idea! Output from amcheck now: WARNING: murray.deanst.rroom.net: selfcheck request timed out. Host down? Now it looks like xinetd had some problem with it. Is there something listening on port 10080/udp? Is there a debugfile created (/tmp/amanda/amandad.*.debug)? What is in it? Since changing the user in xinetd to 'amandabackup' there haven't been any debug files. I checked by putting 'amanda' back in there and restarting xinetd and I did get another debug file, complaining that access as amandabackup is not allowed from [EMAIL PROTECTED] The user that you put in there must exist in the system (password, NIS,...). And the name of that user should be the one that the program has compiled in. You find those defaults in the debug file, which seems to mysteriously disappear... You cannot make something up. So you put amanda in there, and you got a debug file. What errors did you find in that file? When putting amandabackup in the xinetd.conf file, you claim there are no debug files and you get a selfcheck timeout. Right? That means to me that amandabackup is not a valid user or is not correctly defined (for xinetd). I strongly suspect a problem with that user? Do you have a uid-clash (two users with different name, but same uid-number)? Is there a local and a NIS-user that are different? -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: new linux client install
Stefan G. Weichinger wrote: John Clement schrieb: Paul Bijnens wrote: Is there a debugfile created (/tmp/amanda/amandad.*.debug)? What is in it? Since changing the user in xinetd to 'amandabackup' there haven't been any debug files. I checked by putting 'amanda' back in there and restarting xinetd and I did get another debug file, complaining that access as amandabackup is not allowed from [EMAIL PROTECTED] amanad? Third variation now ... check for typos in there. If ok, show us .amandahosts AND Output of amcheck again. -- Decide for one user, amanda OR amandabackup. What user did you configure/compile Amanda with? Make sure that user exists on that system, add it to the disk-group. Stefan OK guys, 'amanad' was my typo copying the message into the email, here's .amandahosts orinoco.deanst.rroom.netamanda orinoco amanda and amcheck WARNING: murray.deanst.rroom.net: selfcheck request timed out. Host down? I didn't install the server or most of the clients here, I only added a client to this particular host yesterday using an RPM, as far as I remember it didn't ask me to configure what user it runs under. Can you point me in the right direction to configuring it to run as 'amanda' which appears to be how its set on the server... Thanks again, John
Re: new linux client install
John Clement schrieb: OK guys, 'amanad' was my typo copying the message into the email, here's .amandahosts Expected this, yes ... orinoco.deanst.rroom.netamanda orinoco amanda and amcheck WARNING: murray.deanst.rroom.net: selfcheck request timed out. Host down? Does not sound like a wrong .amandahosts ... More details (maybe you posted them earlier ..? ): What is your Amanda-server's fqdn? What's the fqdn of the client? I didn't install the server or most of the clients here, I only added a client to this particular host yesterday using an RPM, as far as I remember it didn't ask me to configure what user it runs under. Can you point me in the right direction to configuring it to run as 'amanda' which appears to be how its set on the server... Run amadmin conf version and look for something like : CONFIGURE_COMMAND='./configure' '--with-user=amanda' '--with-group=disk' [...] This way you find out the user and the group it was compiled with/for. Stefan
Re: new linux client install
Paul Bijnens wrote: On 2006-04-26 15:59, John Clement wrote: Paul Bijnens wrote: On 2006-04-26 12:03, John Clement wrote: /, /var, /lib, /var/lib/amanda are all readable. To be complete, they should also be executable. Just made that change. Do you mean that one of the directories were not executable before, but now is? Just the file wasn't executable, I didn't think it had to be, but I've made it so now. Oh yea, restarting xinetd, probably a good idea! Output from amcheck now: WARNING: murray.deanst.rroom.net: selfcheck request timed out. Host down? Now it looks like xinetd had some problem with it. Is there something listening on port 10080/udp? Is there a debugfile created (/tmp/amanda/amandad.*.debug)? What is in it? Since changing the user in xinetd to 'amandabackup' there haven't been any debug files. I checked by putting 'amanda' back in there and restarting xinetd and I did get another debug file, complaining that access as amandabackup is not allowed from [EMAIL PROTECTED] The user that you put in there must exist in the system (password, NIS,...). And the name of that user should be the one that the program has compiled in. You find those defaults in the debug file, which seems to mysteriously disappear... You cannot make something up. Checking one of the debug files it was compiled with amandabackup as the user. So you put amanda in there, and you got a debug file. What errors did you find in that file? ERROR access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amand ahosts: Permission denied When putting amandabackup in the xinetd.conf file, you claim there are no debug files and you get a selfcheck timeout. Right? That means to me that amandabackup is not a valid user or is not correctly defined (for xinetd). I strongly suspect a problem with that user? Do you have a uid-clash (two users with different name, but same uid-number)? Is there a local and a NIS-user that are different? Having run several times with amanda and amandabackup as the user in xinetd, its definately not making any debug files in /tmp/amanda when xinetd's user is set to amandabackup, I've double checked that amandabackup is a valid user, and that there's no uid clash either. Thanks
Re: new linux client install
Stefan G. Weichinger wrote: John Clement schrieb: OK guys, 'amanad' was my typo copying the message into the email, here's .amandahosts Expected this, yes ... orinoco.deanst.rroom.netamanda orinoco amanda and amcheck WARNING: murray.deanst.rroom.net: selfcheck request timed out. Host down? Does not sound like a wrong .amandahosts ... More details (maybe you posted them earlier ..? ): What is your Amanda-server's fqdn? What's the fqdn of the client? server: orinoco.deanst.rroom.net client: murray.deanst.rroom.net and digging on both servers confirms they know who they are and who each other are. I didn't install the server or most of the clients here, I only added a client to this particular host yesterday using an RPM, as far as I remember it didn't ask me to configure what user it runs under. Can you point me in the right direction to configuring it to run as 'amanda' which appears to be how its set on the server... Run amadmin conf version and look for something like : CONFIGURE_COMMAND='./configure' '--with-user=amanda' '--with-group=disk' [...] This way you find out the user and the group it was compiled with/for. server: user: amanda group: disk however I can't find amadmin on the client, at all (find / -name amadmin -print), although one of the debug files shows the following: user: amandabackup group: disk Thanks, john Stefan
Re: new linux client install
John Clement schrieb: Paul Bijnens wrote: On 2006-04-26 15:59, John Clement wrote: Paul Bijnens wrote: On 2006-04-26 12:03, John Clement wrote: /, /var, /lib, /var/lib/amanda are all readable. To be complete, they should also be executable. Just made that change. Do you mean that one of the directories were not executable before, but now is? Just the file wasn't executable, I didn't think it had to be, but I've made it so now. Oh yea, restarting xinetd, probably a good idea! Output from amcheck now: WARNING: murray.deanst.rroom.net: selfcheck request timed out. Host down? Now it looks like xinetd had some problem with it. Is there something listening on port 10080/udp? Is there a debugfile created (/tmp/amanda/amandad.*.debug)? What is in it? Since changing the user in xinetd to 'amandabackup' there haven't been any debug files. I checked by putting 'amanda' back in there and restarting xinetd and I did get another debug file, complaining that access as amandabackup is not allowed from [EMAIL PROTECTED] The user that you put in there must exist in the system (password, NIS,...). And the name of that user should be the one that the program has compiled in. You find those defaults in the debug file, which seems to mysteriously disappear... You cannot make something up. Checking one of the debug files it was compiled with amandabackup as the user. So you put amanda in there, and you got a debug file. What errors did you find in that file? ERROR access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amand ahosts: Permission denied You have to have orinoco amandabackup in your .amandahosts, btw (apart from the perms-problem). The server is orinoco? And there Amanda runs as amandabackup? And tries to contact the client on murray which runs as amandabackup as well?? When putting amandabackup in the xinetd.conf file, you claim there are no debug files and you get a selfcheck timeout. Right? That means to me that amandabackup is not a valid user or is not correctly defined (for xinetd). I strongly suspect a problem with that user? Do you have a uid-clash (two users with different name, but same uid-number)? Is there a local and a NIS-user that are different? Having run several times with amanda and amandabackup as the user in xinetd, its definately not making any debug files in /tmp/amanda when xinetd's user is set to amandabackup, I've double checked that amandabackup is a valid user, and that there's no uid clash either. grep amanda /etc/passwd Different group-memberships of amanda and amandabackup? Stefan
Re: new linux client install
Stefan G. Weichinger wrote: John Clement schrieb: Paul Bijnens wrote: On 2006-04-26 15:59, John Clement wrote: Paul Bijnens wrote: On 2006-04-26 12:03, John Clement wrote: /, /var, /lib, /var/lib/amanda are all readable. To be complete, they should also be executable. Just made that change. Do you mean that one of the directories were not executable before, but now is? Just the file wasn't executable, I didn't think it had to be, but I've made it so now. Oh yea, restarting xinetd, probably a good idea! Output from amcheck now: WARNING: murray.deanst.rroom.net: selfcheck request timed out. Host down? Now it looks like xinetd had some problem with it. Is there something listening on port 10080/udp? Is there a debugfile created (/tmp/amanda/amandad.*.debug)? What is in it? Since changing the user in xinetd to 'amandabackup' there haven't been any debug files. I checked by putting 'amanda' back in there and restarting xinetd and I did get another debug file, complaining that access as amandabackup is not allowed from [EMAIL PROTECTED] The user that you put in there must exist in the system (password, NIS,...). And the name of that user should be the one that the program has compiled in. You find those defaults in the debug file, which seems to mysteriously disappear... You cannot make something up. Checking one of the debug files it was compiled with amandabackup as the user. So you put amanda in there, and you got a debug file. What errors did you find in that file? ERROR access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amand ahosts: Permission denied You have to have orinoco amandabackup in your .amandahosts, btw (apart from the perms-problem). The server is orinoco? And there Amanda runs as amandabackup? And tries to contact the client on murray which runs as amandabackup as well?? OK, I've re-added orinoco amandabackup orinoco.deanst.rroom.net amandabackup to the .amandahosts file, on orinoco (the server) it runs as 'amanda', on the client it runs as 'amandabackup'. When putting amandabackup in the xinetd.conf file, you claim there are no debug files and you get a selfcheck timeout. Right? That means to me that amandabackup is not a valid user or is not correctly defined (for xinetd). I strongly suspect a problem with that user? Do you have a uid-clash (two users with different name, but same uid-number)? Is there a local and a NIS-user that are different? Having run several times with amanda and amandabackup as the user in xinetd, its definately not making any debug files in /tmp/amanda when xinetd's user is set to amandabackup, I've double checked that amandabackup is a valid user, and that there's no uid clash either. grep amanda /etc/passwd Different group-memberships of amanda and amandabackup? Stefan amanda and amandabackup are both members of the disk group. Cheers
Re: new linux client install
On 2006-04-26 17:23, John Clement wrote: Paul Bijnens wrote: On 2006-04-26 15:59, John Clement wrote: Paul Bijnens wrote: On 2006-04-26 12:03, John Clement wrote: /, /var, /lib, /var/lib/amanda are all readable. To be complete, they should also be executable. Just made that change. Do you mean that one of the directories were not executable before, but now is? Just the file wasn't executable, I didn't think it had to be, but I've made it so now. The FILE does not need to be executable. The DIRECTORIES must be executable. You're making things so confusing... ERROR access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amand ahosts: Permission denied Having run several times with amanda and amandabackup as the user in xinetd, its definately not making any debug files in /tmp/amanda when xinetd's user is set to amandabackup, I've double checked that amandabackup is a valid user, and that there's no uid clash either. I think I see the light... :-) The /tmp/amanda directory is owned by the wrong user! So do you mean that you have both a user amanda AND a user amandabackup? 1. When you put user amanda in the xinetd conf file, you do get a debug file, and you get the errormessage: access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: Permission denied. I can understand the Permission denied error here: the file is owned by user amandabackup, and user amanda does not have access to the file. I do not understand why the programs says it runs as user amandabackup while you clearly state that you run it as amanda. 2. When you put user amandabackup in xinetd conf file, you do NOT get a debug file at all. That means that xinetd didn't even got the program to START (any error in /var/log/messages?) but also that the debug file could not be created. Amandad tries to create the debug file the directory /tmp/amanda, but that was created on the first run with the wrong owner: amanda instead of amandabackup. ERASE the directory /tmp/amanda, and then try to run again with user amandabackup in the xinetd conf file. And let us know the complete error message. (Do not forget to signal xinetd if you made changes to the config file.) -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: new linux client install
On 2006-04-26 17:58, John Clement wrote: OK, I've re-added orinoco amandabackup orinoco.deanst.rroom.net amandabackup to the .amandahosts file, I'm sorry to tell you the bad news that this is again WRONG. on orinoco (the server) it runs as 'amanda', on the client it runs as 'amandabackup'. The error message that you get is: ... access as localuser not allowed from [EMAIL PROTECTED] : ... The LOCALUSER = amandabackup the REMOTEUSER on the AMANDASERVER is [EMAIL PROTECTED] The LOCALUSER must be able to read the file .amandahosts and in that file it finds the name of the AMANDASERVER, and the user on that server that is allowed to give orders here: amandaserver.example.com amandauserontheserver In your case: orinoco amanda. See also: http://wiki.zmanda.com/index.php/Amcheck:_access_as_localuser_not_allowed_from_remoteuser%40remotehost btw: your problem with permission of /tmp/amanda is described as one of the cause here: http://wiki.zmanda.com/index.php/Amcheck:_selfcheck_request_timed_out (i.e. exactly the error message you got) -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: new linux client install
Paul Bijnens schrieb: I think I see the light... :-) The /tmp/amanda directory is owned by the wrong user! or is not writable by the amanda-user, yes ... I saw that light also ;-) Let's see if it gets through now ... Stefan
new linux client install
Having read through some of the documentation it seemed a fairly straight forward thing to install an Amanda client. However, I used an rpm for it, having been forced to upgrade my tar software too but it appears to be running as amandabackup and in /var/lib... So I'm now getting the following: amandad: time 0.002: accept error: access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: Permission denied amandad: time 0.002: sending NAK pkt: ERROR access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: Permission denied at the bottom of my amcheck. I've confirmed that the file is owned and chmoded correctly: -rw--- 1 amandabackup disk 109 Apr 25 14:23 .amandahosts If I change the ownership or permissions it complains, so I think they are correct. In the .amandahosts file I have server.domain.tld amanda server amanda server.domain.tld amandabackup #added incase it made a difference server amandabackup #added incase it made a difference So can anyone make any suggestions? Thanks
Re: new linux client install
John Clement wrote: Having read through some of the documentation it seemed a fairly straight forward thing to install an Amanda client. However, I used an rpm for it, having been forced to upgrade my tar software too but it appears to be running as amandabackup and in /var/lib... So I'm now getting the following: amandad: time 0.002: accept error: access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: Permission denied amandad: time 0.002: sending NAK pkt: ERROR access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: Permission denied at the bottom of my amcheck. I've confirmed that the file is owned and chmoded correctly: -rw--- 1 amandabackup disk 109 Apr 25 14:23 .amandahosts If I change the ownership or permissions it complains, so I think they are correct. In the .amandahosts file I have server.domain.tld amanda server amanda server.domain.tld amandabackup #added incase it made a difference server amandabackup #added incase it made a difference So can anyone make any suggestions? Thanks make sure that /var/lib/amanda/.amandahosts is owned by amanda and the group is set to disk chown amanda:disk /var/lib/amanda/.amandahosts
Re: new linux client install
On 2006-04-25 16:35, John Clement wrote: Having read through some of the documentation it seemed a fairly straight forward thing to install an Amanda client. However, I used an rpm for it, having been forced to upgrade my tar software too but it appears to be running as amandabackup and in /var/lib... So I'm now getting the following: amandad: time 0.002: accept error: access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: Permission denied amandad: time 0.002: sending NAK pkt: ERROR access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: Permission denied at the bottom of my amcheck. I've confirmed that the file is owned and chmoded correctly: -rw--- 1 amandabackup disk 109 Apr 25 14:23 .amandahosts Seems ok. Check the directories /var /var/lib and /var/lib/amanda too for access as amandabackup. If I change the ownership or permissions it complains, so I think they are correct. In the .amandahosts file I have server.domain.tld amanda server amanda server.domain.tld amandabackup #added incase it made a difference server amandabackup #added incase it made a difference The last two lines are not needed. This is enough (note the errors message above): orinoco amanda -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: new linux client install
John Clement wrote: Having read through some of the documentation it seemed a fairly straight forward thing to install an Amanda client. However, I used an rpm for it, having been forced to upgrade my tar software too but it appears to be running as amandabackup and in /var/lib... So I'm now getting the following: amandad: time 0.002: accept error: access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: Permission denied amandad: time 0.002: sending NAK pkt: ERROR access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: Permission denied at the bottom of my amcheck. I've confirmed that the file is owned and chmoded correctly: -rw--- 1 amandabackup disk 109 Apr 25 14:23 .amandahosts If I change the ownership or permissions it complains, so I think they are correct. In the .amandahosts file I have server.domain.tld amanda server amanda server.domain.tld amandabackup #added incase it made a difference server amandabackup #added incase it made a difference So can anyone make any suggestions? I suspect that amandad on the client was started by amanda (instead of amandabackup as it should be). could you show the content of /etc/xinetd.d/amanda* #cat /etc/xinetd.d/amanda* the user field should be amandabackup -- Thank you! Kevin Till Amanda documentation: http://wiki.zmanda.com Amanda forums:http://forums.zmanda.com
Re: Client install tree
LaValley, Brian E wrote: Does the install location have to be the same on the server and all the clients? I'm not 100% sure, but it seems to me that it shouldn't have to be. As long as the daemons are listening on the proper ports, it should work. -- Graeme Humphries ([EMAIL PROTECTED]) (306) 955-7075 ext. 485 My views are not the views of my employers.
Re: Client install tree
On Monday 08 August 2005 13:10, LaValley, Brian E wrote: Does the install location have to be the same on the server and all the clients? No. Paths that are important are ./configured into it when installing, but as long as they are good paths, it shouldn't be a problem. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.35% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: Client install tree
If you plan on using amverify, you should make sure that the GNU tar path is the same on all of your systems, or amverify will report errors like this: Skipped sbsdp._var_spool_cron_crontabs.20050729.1 (** Cannot do /usr/local/libexec/amtar dumps) Anthony Valentine Gene Heskett wrote: On Monday 08 August 2005 13:10, LaValley, Brian E wrote: Does the install location have to be the same on the server and all the clients? No. Paths that are important are ./configured into it when installing, but as long as they are good paths, it shouldn't be a problem. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.35% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: Client install
I agree, this topic is largely uncovered in the documentation. I spent several days trying to figure out how to set things up, until I realized that amanda had to be installed in full on the client machines as well. I had incorrectly assumed that amanda used some kind of UNIX networking to suck the data from the client computers, but I was confused as to why I never had to specify any authentication to be able to access those computers. As for massive overkill, it only installs less than a meg of binaries on each client. Not too bad. Compare that with Windows bloatware, and it's microscopic. :) Eric Wadsworth On Wed, 29 Nov 2000, Harri Haataja wrote: On Tue, 28 Nov 2000, Randolph Cordell wrote: How is installing for the clients different than for the server? That is not evident in anything I've read (README, INSTALL and the entire chapter online at www.amanda.org). Do I need to do the whole ./configure, make, make install process for each client? IT seems that's massive overkill. You can configure them --without-server. Otherwise, it's pretty much the same.
Client install
Hey John, How is installing for the clients different than for the server? That is not evident in anything I've read (README, INSTALL and the entire chapter online at www.amanda.org). Do I need to do the whole ./configure, make, make install process for each client? IT seems that's massive overkill. Randy Cordell __ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/
