Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19

Thread: problem with amcheck freebsd

  1. #11
    Join Date
    May 2008
    Posts
    45

    Default

    Could you do

    sudo -u amandabackup ls

    so we can see if it can be execed to?

    /glz

  2. #12
    Join Date
    Sep 2008
    Posts
    32

    Default

    Code:
    [root@myFreeBsd ~]# sudo -u amandabackup ls
    bash: sudo: command not found
    I dont' have sudo installed on this machine, and it won't be. It's not my decision and I can't do anything about this....

  3. #13
    Join Date
    Mar 2007
    Location
    Chicago, IL
    Posts
    688

    Default

    What glowkrantz is getting at is that you should test that the amandabackup user is functional for you, through whatever means you do have available.

  4. #14
    Join Date
    Sep 2008
    Posts
    32

    Default

    well then... I misunderstood Him. So here We go:

    Code:
    [root@myFreeBsd ~]# su - amandabackup
    [amandabackup@myFreeBsd ~]$ ls
    [amandabackup@myFreeBsd ~]$ pwd
    /usr/local/etc/amanda
    [amandabackup@myFreeBsd ~]$ am<tab>
    amaespipe          amcrypt-ossl       amcryptsimple      amgpgcrypt         amq
    amcrypt            amcrypt-ossl-asym  amd                amoldrecover       amrecover
    [amandabackup@myFreeBsd  ~]$ cat .amandahosts
    192.168.4.3     amanda  amdump
    192.168.4.4     amanda  amdump
    [amandabackup@ myFreeBsd  ~]$ ping 192.168.4.3
    PING 192.168.4.3 (192.168.4.3): 56 data bytes
    64 bytes from 192.168.4.3: icmp_seq=0 ttl=255 time=0.267 ms
    64 bytes from 192.168.4.3: icmp_seq=1 ttl=255 time=0.240 ms
    ^C
    --- 192.168.4.3 ping statistics ---
    2 packets transmitted, 2 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 0.240/0.254/0.267/0.013 ms
    [amandabackup@ myFreeBsd  ~]$ ping 192.168.4.4
    PING 192.168.4.4 (192.168.4.4): 56 data bytes
    64 bytes from 192.168.4.4: icmp_seq=0 ttl=255 time=0.541 ms
    64 bytes from 192.168.4.4: icmp_seq=1 ttl=255 time=0.247 ms
    64 bytes from 192.168.4.4: icmp_seq=2 ttl=255 time=0.251 ms
    ^C
    --- 192.168.4.4 ping statistics ---
    3 packets transmitted, 3 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 0.247/0.346/0.541/0.138 ms
    what else should I check?

    regards,
    Michał

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

    Default

    inetd doesn't have the permission to execute the initgroups call, you should check the inetd permissions and ask on a FreeBSD mailling list.

  6. #16
    Join Date
    May 2008
    Posts
    45

    Default

    Also verify the uid and group of amandbackup:

    As amandabckup

    id

    and as root

    id amandabackup.

    and post the output.

    /glz

  7. #17
    Join Date
    Sep 2008
    Posts
    32

    Default

    hello,

    Code:
    [root@myFreeBsd ~]# id amandabackup
    uid=1005(amandabackup) gid=0(wheel) groups=0(wheel)
    [root@myFreeBsd ~]# su - amandabackup
    [amandabackup@myFreeBsd ~]$ id
    uid=1005(amandabackup) gid=0(wheel) groups=0(wheel)
    so that's right... and what is the cause You said with inetd?

    regards,
    Michał

  8. #18
    Join Date
    May 2008
    Posts
    45

    Default

    OK, just few more things to test before I start looking at the source.

    1: If you change the run-as-user to root, what happens?
    2: Try setting the primary group of amandabackup user to operator and test again.
    3: If you use the default backup user of freebsd, operator, does amandad start?

    Point 3 would require you to rebuild the software but please test it if you have time,.

    And why don't you use the port? It's known to work. You can always use a lower version client, as it's currently 2.5.2. If you need 2.6.0 we have a working port of it, the maintainer has not had time to commit it.

    /glz
    Last edited by glowkrantz; October 16th, 2008 at 10:42 PM. Reason: Wording, spelling

  9. #19
    Join Date
    Sep 2008
    Posts
    32

    Default

    ok, problem is resolved... the problem was, as You said, with inetd. Something was fu**** up, it didn't start properly, now we have xinetd on this machine and everything works as it should.... thanks again for Your help.

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
  •