Results 1 to 6 of 6

Thread: tcpm_recv_token: invalid size: amandad:

  1. #1
    Join Date
    Oct 2008
    Location
    Campinas-SP
    Posts
    34

    Default tcpm_recv_token: invalid size: amandad:

    Gosh, another issue...

    I am using amanda server 2.6.0p2 on a openSuSE.
    The server is already running for a few weeks and it has just one another openSuSE client - no problems.

    Today I added another client; a Fedora 8, running amanda_client 2.6.0p2-1.fc8.

    The problem is amcheck is returning a error on that new client:
    Code:
    Amanda Backup Client Hosts Check
    --------------------------------
    WARNING: agente86: selfcheck request failed: tcpm_recv_token: invalid size: amandad: 
    Client check: 3 hosts checked in 1.121 seconds.  1 problem found.
    This new client has the firewall disabled and selinux running on permissive mode.
    I am using auth bsdtcp and the xinetd file is the same as /var/lib/amanda/example/xinetd.amandaclient which was installed by the rpm's postinstall script (I guess).

    On the client, the content of /var/lib/amanda/.amandahosts is: (bigslam is my amanda server)
    Code:
    localhost   amandabackup amdump
    localhost.localdomain   amandabackup amdump
    bigslam.apice.com.br amandabackup amdump
    It is the same content I am using on the another openSuSE client.

    The content of the amcheck.*.debug is attached. You will see the new client on the debug file as 192.168.160.252 starting at line 29.
    Attached Files Attached Files

  2. #2
    Join Date
    Nov 2005
    Location
    Canada
    Posts
    1,049

    Default

    Did it produce and amanda.*.debug file on the client? Can you post it?
    Any system error message on the client about amandad?
    It could be a missing package, what do you if you run amandad on the client?

  3. #3
    Join Date
    Oct 2008
    Location
    Campinas-SP
    Posts
    34

    Default

    Quote Originally Posted by martineau View Post
    Did it produce and amanda.*.debug file on the client? Can you post it?
    No, there is no new files on /var/log/amanda. Just old files from the previous version 2.5.2p1.


    Quote Originally Posted by martineau View Post
    Any system error message on the client about amandad?
    Yes, there is, but not anything it can give hints, at least for me.
    The old amanda package (2.5.2p1) was un-installed on Dec 3 15:17:23 or about.
    The new amanda package was installed on Dec 3 16:25:47 (or close to it).
    I guess the first amcheck was done on Dec 3 16:29:32.

    Code:
    Dec  3 15:17:23 agente86 xinetd[2088]: service amanda deactivated
    Dec  3 15:17:23 agente86 xinetd[2088]: amanda: svc_release with 0 count
    Dec  3 16:25:47 agente86 setroubleshoot: SELinux is preventing the useradd from using potentially mislabeled files (/tmp/rpm-amanda.BKQSvm19049). For complete SELinux messages. run sealert -l 8be7d886-34b0-456c-9505-b9750759f97e
    Dec  3 16:25:47 agente86 setroubleshoot: SELinux is preventing the useradd from using potentially mislabeled files (/tmp/rpm-amanda.BKQSvm19049). For complete SELinux messages. run sealert -l 36e6c687-3922-4024-a662-dfa6acd4a211
    Dec  3 16:25:47 agente86 setroubleshoot: SELinux is preventing the nscd from using potentially mislabeled files (/tmp/rpm-amanda.BKQSvm19049). For complete SELinux messages. run sealert -l 1be29385-8ef4-400f-8e0a-5f9416ba1428
    Dec  3 16:25:49 agente86 xinetd[19103]: Service amanda: attribute already set: flags [file=/etc/xinetd.d/amandaclient] [line=10]
    Dec  3 16:29:32 agente86 xinetd[19103]: START: amanda pid=24751 from=192.168.160.253
    Dec  3 16:29:33 agente86 xinetd[19103]: EXIT: amanda status=1 pid=24751 duration=1(sec)
    Dec  3 16:31:55 agente86 xinetd[19103]: Service amanda: attribute already set: flags [file=/etc/xinetd.d/amandaclient] [line=10]
    Dec  3 16:31:55 agente86 xinetd[19103]: readjusting service amanda
    Dec  3 16:32:01 agente86 xinetd[19103]: START: amanda pid=29380 from=192.168.160.253
    Dec  3 16:32:01 agente86 xinetd[19103]: EXIT: amanda status=1 pid=29380 duration=0(sec)
    Dec  3 16:41:49 agente86 xinetd[19103]: Service amanda: attribute already set: flags [file=/etc/xinetd.d/amandaclient] [line=10]
    Dec  3 16:41:49 agente86 xinetd[19103]: readjusting service amanda
    Dec  3 16:41:54 agente86 xinetd[19103]: START: amanda pid=13924 from=192.168.160.253
    Dec  3 16:41:54 agente86 xinetd[19103]: EXIT: amanda status=1 pid=13924 duration=0(sec)
    Dec  3 16:42:30 agente86 xinetd[19103]: Service amanda: attribute already set: flags [file=/etc/xinetd.d/amandaclient] [line=10]
    Dec  3 16:42:30 agente86 xinetd[19103]: readjusting service amanda
    Dec  3 16:44:06 agente86 xinetd[19103]: START: amanda pid=17392 from=192.168.160.253
    Dec  3 16:44:06 agente86 xinetd[19103]: EXIT: amanda status=1 pid=17392 duration=0(sec)
    Dec  3 16:44:39 agente86 xinetd[19103]: START: amanda pid=18828 from=192.168.160.253
    Dec  3 16:44:39 agente86 xinetd[19103]: EXIT: amanda status=1 pid=18828 duration=0(sec)
    Dec  3 17:26:43 agente86 xinetd[19103]: START: amanda pid=25188 from=192.168.160.253
    Dec  3 17:26:44 agente86 xinetd[19103]: EXIT: amanda status=1 pid=25188 duration=1(sec)
    Dec  4 08:23:51 agente86 xinetd[19103]: START: amanda pid=19642 from=192.168.160.253
    Dec  4 08:23:52 agente86 xinetd[19103]: EXIT: amanda status=0 pid=19642 duration=1(sec)
    Dec  4 08:25:21 agente86 xinetd[19103]: START: amanda pid=21672 from=192.168.160.253
    Dec  4 08:25:21 agente86 xinetd[19103]: EXIT: amanda status=0 pid=21672 duration=0(sec)
    Quote Originally Posted by martineau
    It could be a missing package, what do you if you run amandad on the client?
    how I do that ? I tried:
    Code:
    /bin/su - amandabackup -c "/usr/libexec/amanda/amandad -auth=bsdtcp amdump"
    but it not "sticks" there....looks like it terminates right away....
    Last edited by marozsas; December 4th, 2008 at 01:49 AM.

  4. #4
    Join Date
    Aug 2008
    Location
    Sunnyvale, CA
    Posts
    306

    Default

    Your guess on running amandad was excellent and I believe when martineau asks about any "amanda.*.debug" logs he means "amandad.*.debug" (notice the second "d"). What you executed should have produced a log in /var/log/amanda/amandad/. Also, running amandad without any options should take much longer and the point of this is to see that /usr/libexec/amanda/amandad runs without any standard error to the terminal, ie. a missing library, etc. As this latter does not seem to be the case, the next step would be to look through the amandad log itself for any clues. If this all looks good, an amcheck from the server should also produce an amandad log. I see two "status=0" runs in your system logs for Dec. 4 from supposedly amchecks from the server which is a good sign of things working.

  5. #5
    Join Date
    Oct 2008
    Location
    Campinas-SP
    Posts
    34

    Default

    SOLVED !

    Hi pyeatman, hi martineau
    I was wondering why there is no new amandad.*.debug files on client that Martineau asks and Pyeatman re-enforced.
    I realize /tmp/amanda and /var/log/amanda has wrong owner. It was user "amanda" but it is suppose to be "amandabackup" ! And this is why the new files was not created !

    I guess when I remove the old rpm package 2.5 it didn't remove theses directories and when I installed the new 2.6 rpm package it (it, the postinstall scripts) didn't updated the owner. (You known, in 2.5 the amanda user is "amanda" and in 2.6 series it is "amandabackup")

    I simple "chown -R amandabackup:disk /var/log/amanda /tmp/amanda" did the trick and everything is fine now.

    Thanks a lot for the help, guys !

    PS: It is a shame there is no indication whatsoever there was a file access problem anywhere...

  6. #6
    Join Date
    Nov 2005
    Location
    Canada
    Posts
    1,049

    Default

    The error should be reported by amcheck, I get:
    WARNING: localhost.localdomain: selfcheck request failed: tcpm_recv_token: invalid size: amandad: critical (fatal): open debug directory "/tmp/amanda/amandad/": Permission denied

    I don't understand why the message you get was trunked.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •