[Bug 918247] New: application amanda: setup seems wrong: selfcheck request failed: Connection refused
http://bugzilla.opensuse.org/show_bug.cgi?id=918247 Bug ID: 918247 Summary: application amanda: setup seems wrong: selfcheck request failed: Connection refused Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: AutoYaST Assignee: autoyast-maintainers@suse.de Reporter: lee4home@btinternet.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0 Build Identifier: Application is amanda 3.3.6, released 07/09/2014; but documentation from 2007 is not helpful as it is contradicted by web chat. Immediate problem: "amcheck DailySet1" produces "selfcheck request failed: Connection refused". This sounds like an authentication issue, perhaps due to inconsistent setup files. However, necessary setup seems to be changed from previous SuSE distributions, perhaps because of changes in xinetd. I have tried permutations of suggestions from web advice, but am now merely confused. Will attach file details. Reproducible: Always Steps to Reproduce: After file and yast2 => xinetd setup (which does not seem to be automatic), first steps are "amcheck DailySet1" which gives rise to symptoms as stated. Actual Results: Amanda Backup Client Hosts Check -------------------------------- WARNING: mozart: selfcheck request failed: Connection refused Client check: 1 host checked in 10.021 seconds. 1 problem found. Expected Results: 0 problems found. See attachment. amanda has been a stalwart backup system over many years, but appears broken here. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=918247 Martin Pluskal <mpluskal@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kstreitova@suse.com, | |mpluskal@suse.com Component|AutoYaST |Basesystem Assignee|autoyast-maintainers@suse.d |bnc-team-screening@forge.pr |e |ovo.novell.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=918247 --- Comment #1 from Anthony Lee <lee4home@btinternet.com> --- Created attachment 623577 --> http://bugzilla.opensuse.org/attachment.cgi?id=623577&action=edit Relevant setup data, and test/debug results xinetd entries from /etc/xinetd.d: amanda, amandaidx, amidxtape, as currently configured (after trying to follow internet advice: may be inconsistent). Note one internet comment was that only 1 entry was now necessary, not three. Queries on some entries: help sought. Symptoms: => selfcheck request failed: Connection refused. Debug details: Nothing on comms. Some exploration: amcheck -lt DailySet1, amcheck --client-verbose DailySet1, with debug: again, not helpful. Comms Tests: telnet mozart, telnet mozart 10080: latter is refused. Significant? amanda-client.conf Extract from amanda.conf I can obviously provide further diagnostic tests if needed, but I suspect I need help from someone with more knowledge of current amanda, and also knowledge of constraints imposed by SuSE. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=918247 --- Comment #2 from Anthony Lee <lee4home@btinternet.com> --- With current test setup, the "client" system is "mozart", which is also the server system --- at present no other machines are involved, although they will be eventually. Extract from disklist, stuff like: mozart /raid/etc comp-user-tar mozart /raid/var comp-user-tar mozart /raid/opt/NAG comp-user-tar #mozart //ronnie/Tony2 comp-user-tar-samba #mozart //ronnie/arc0 comp-user-tar-samba where the samba stuff has been commented out for the moment. Note these entries have worked for years with earlier versions of amanda, and have their appropriate "amanda.exclude" files. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=918247 Bernhard Wiedemann <bwiedemann@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |darin@darins.net Assignee|bnc-team-screening@forge.pr |kstreitova@suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=918247 Anthony Lee <lee4home@btinternet.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #623577|0 |1 is obsolete| | --- Comment #3 from Anthony Lee <lee4home@btinternet.com> --- Created attachment 624096 --> http://bugzilla.opensuse.org/attachment.cgi?id=624096&action=edit xinetd entries for successful amcheck Eventually found xinetd entries that worked as far as amcheck --- these are not the same as the amanda distribution for SuSE, and do not follow what appears to be current advice on zmanda (which seems to suggest use of dgram and udp). Note: needed to preserve some files (eg data contents of existing backups), so had to check ownership, permissions etc. Slow progress because I powered down then booted up after each change to xinetd. Once you have changed xinetd using yast2, how can you reliably re-start xinetd without reboot? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=918247 --- Comment #4 from Anthony Lee <lee4home@btinternet.com> --- Comment on attachment 624096 --> http://bugzilla.opensuse.org/attachment.cgi?id=624096 xinetd entries for successful amcheck Query I originally made now solved, but my solution suggests the amanda distribution for SuSE may need changes. Seek advice on the method I used. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com