FS#6364 - bitlbee defunct after xinetd-update

Attached to Project: Arch Linux
Opened by Christian Schmidt (mucknert) - Wednesday, 07 February 2007, 10:37 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 11 November 2007, 10:49 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Simo Leone (neotuli)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

After the latest xinetd-Update (2.3.14-2), the user is unable to connect to it. This has been confirmed by various users. Other software like vmware-server still works.
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Sunday, 11 November 2007, 10:49 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed for submitter (see forum post). Other commenter has not responded.
Comment by Christian Schmidt (mucknert) - Wednesday, 07 February 2007, 10:42 GMT
After configuring xinetd to dump logs to its own file I get the following:

07/2/7@11:41:16: START: bitlbee pid=11463 from=127.0.0.1
07/2/7@11:41:17: FAIL: bitlbee libwrap from=127.0.0.1

HTH
Comment by Dieter Rethmeyer (Dieter) - Wednesday, 07 February 2007, 16:42 GMT
I noticed that my pop3 server controlled by xinetd stopped working, too after the xinetd update. No more mail delivery to MUAs any more. So it seems to be a more general problem with the xinetd services than only bitlbee. I assume an upstream problem as I also noticed similar problems in my debian system (with inetd, not xinetd).
Comment by Christian Schmidt (mucknert) - Wednesday, 07 February 2007, 19:17 GMT
http://bbs.archlinux.org/viewtopic.php?pid=227820

Does that work for your MUA, Dieter?

Loading...