Re: [arch-general] The vsftpd only starts at the second attempt
Lucas Salies Brum wrote: (r...@abraham ~):# ps -A | grep vsftpd (r...@abraham ~):# /etc/rc.d/vsftpd start :: Starting vsftpd FTP Daemon [FAIL] (r...@abraham ~):# /etc/rc.d/vsftpd stop :: Stopping vsftpd FTP Daemon [DONE] (r...@abraham ~):# /etc/rc.d/vsftpd start :: Starting vsftpd FTP Daemon [DONE] (r...@abraham ~):# ps -A | grep vsftpd 6453 pts/300:00:00 vsftpd This has happened to someone? /etc/vsftpd.conf - http://paste.archlinux-br.org/1241 /etc/rc.conf - http://paste.archlinux-br.org/1242 Arch Linux i686. Thanks. --- Lucas Saliés Brum http://sistematico.org lsbrum @ irc.freenode.org Not having this problem with the default vsftpd.conf. Instead of starting it via the initscripts, can you start vsftpd manually? Does it fail as well? Can you try strace the process? Glenn
Re: [arch-general] [arch-dev-public] [signoff] udev-145-1
I'll shoot an email to Slicehost on my behalf to see what kernels they have available. What other VPS providers offer Arch? It isn't a tough thing to find out how much we can get away with here. -Dan I think SevenL networks (who provide services to us) offers Arch... Doing a search on google archlinux hosting [1] I found some companies that I didn't notice of their existence in fact. Cheers [1] http://www.google.co.ve/search?hl=esq=archlinux+hostingbtnG=Buscar+con+Googlemeta=aq=foq= -- Angel Velásquez angvp @ irc.freenode.net Linux Counter: #359909
Re: [arch-general] Xorg broken after last update
On Sat-2009/08/01-23:58 Lu?s Moreira wrote: The last update broke my Xorg, the screen just goesn black and hangs there, CTRL+ALT+F1 (etc) doesn't do anything. I'm using X86_64, *without* [testing]. The updated packages were kernel26 nvidia xorg-server (and some others, less important) If I change the driver in xorg.conf from nvidia to vesa X works again. I'm running i686. The nVIDIA GeForce 6100/nFORCE 430 chipset (AMD64) exhibits segfaults in xorg-server-1.6.3-1 X(1): Backtrace: 0: /usr/bin/X(xorg_backtrace+0x3b) [0x813177b] 1: /usr/bin/X(xf86SigHandler+0x9e) [0x80caf6e] 2: [0xb7f79400] 3: /usr/lib/libdbus-1.so.3 [0xb7e884c9] 4: /usr/bin/X [0x80ab683] 5: /usr/bin/X(WakeupHandler+0x52) [0x8090b42] 6: /usr/bin/X(WaitForSomething+0x1a2) [0x812f2b2] 7: /usr/bin/X(Dispatch+0x80) [0x808c530] 8: /usr/bin/X(main+0x395) [0x8072065] 9: /lib/libc.so.6(__libc_start_main+0xe6) [0xb7b45a36] 10: /usr/bin/X [0x8071511] Fatal server error: Caught signal 11. Server aborting This error occurs often, but today another one showed up: Backtrace: 0: /usr/bin/X(xorg_backtrace+0x3b) [0x813177b] 1: /usr/bin/X(xf86SigHandler+0x9e) [0x80caf6e] 2: [0xb7f96400] 3: /usr/lib/libdbus-1.so.3 [0xb7ea54c9] 4: /usr/bin/X [0x80ab683] 5: /usr/bin/X(WakeupHandler+0x52) [0x8090b42] 6: /usr/bin/X(WaitForSomething+0x1a2) [0x812f2b2] 7: /usr/bin/X(Dispatch+0x80) [0x808c530] 8: /usr/bin/X(main+0x395) [0x8072065] 9: /lib/libc.so.6(__libc_start_main+0xe6) [0xb7b62a36] 10: /usr/bin/X [0x8071511] Fatal server error: Caught signal 4. Server aborting Signal 4 is an illegal instruction. The log also contained, for the sigsegv case: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server :0.0 after 27 requests (26 known processed) with 0 events remaining. XIO: fatal IO error 11 (Resource temporarily unavailable) on X server :0.0 after 103 requests (103 known processed) with 0 events remaining. XIO: fatal IO error 11 (Resource temporarily unavailable) on X server :0.0 after 508 requests (508 known processed) with 0 events remaining. urxvt: X connection to ':0.0' broken, unable to recover, exiting. xinit: connection to X server lost. In my case, the error appeared after various intervals of normal operation, but I think I could provoke it by opening more windows. As several components went into the last upgrade, I couldn't tell which one caused the problem. The X11-related packages were: [2009-08-02 16:04] upgraded hal-info (0.20090414-1 - 0.20090716-1) [2009-08-02 16:04] upgraded inputproto (1.5.0-1 - 1.5.1-1) [2009-08-02 16:05] upgraded kernel26 (2.6.30.2-1 - 2.6.30.4-1) [2009-08-02 16:05] upgraded xcb-proto (1.4-1 - 1.5-1) [2009-08-02 16:05] upgraded libxcb (1.2-1 - 1.4-1) [2009-08-02 16:05] upgraded libx11 (1.2.1-1 - 1.2.2-1) [2009-08-02 16:05] upgraded pciutils (3.1.2-1 - 3.1.3-1) [2009-08-02 16:05] upgraded xcb-util (0.3.4-2 - 0.3.5-1) [2009-08-02 16:05] upgraded xf86-input-evdev (2.2.2-1 - 2.2.3-1) [2009-08-02 16:05] upgraded xorg-server (1.6.2-1 - 1.6.3-1) I don't run a customary desktop, just screen(1) in urxvt(1) on Xorg(7), all applications being ncurses driven. Doing: pacman -U /var/cache/pacman/pkg/xorg-server-1.6.2-1-i686.pkg.tar.gz fixed it. BTW: except for one instance where neither mouse nor keyboard worked, I was dropped back to the console and didn't loose any work, because I could resurrect everything with screen -R. It is even possible to experiment within X11, detach that screen and resume it in the console, switching back and forth between X11-grafix and console. A wonderful thing, this screen(1) program! One last thing should be mentioned, though: a few days ago, with xorg-server-1.6.2-1 running, Xorg froze on me, indicating that the problem might not be caused by the hal-debug-patch mentioned in the forum. The more so because I don't have hald(8) running at all, and my /etc/X11/xorg.conf contains: Section ServerFlags ... Option AutoAddDevices False # stop HAL Option AutoEnableDevices false # stop HAL EndSection The DBUS daemon is up, if that is of interest. clemens
[arch-general] Arch minimum kernel version (was: [signoff] udev-145-1)
2009/8/3 Angel Velásquez an...@archlinux.com.ve: I'll shoot an email to Slicehost on my behalf to see what kernels they have available. What other VPS providers offer Arch? It isn't a tough thing to find out how much we can get away with here. -Dan I think SevenL networks (who provide services to us) offers Arch... Doing a search on google archlinux hosting [1] I found some companies that I didn't notice of their existence in fact. Got a response from Slice: The following kernels are available for your slice to upgrade. Please let us know and we can take care of that for you. 2.6.24 - 23.48 2.6.24 - 24.55 I believe these should be Ubuntu kernel versions; I'm seeing right now what they actually include as it might include a fully working signalfd(). If anyone wants to contact some other providers (especially if you are already using their services) and post the response here, that would be cool. -Dan
Re: [arch-general] Arch minimum kernel version (was: [signoff] udev-145-1)
On Mon, Aug 3, 2009 at 10:29 AM, Dan McGeedpmc...@gmail.com wrote: 2009/8/3 Angel Velásquez an...@archlinux.com.ve: I'll shoot an email to Slicehost on my behalf to see what kernels they have available. What other VPS providers offer Arch? It isn't a tough thing to find out how much we can get away with here. -Dan I think SevenL networks (who provide services to us) offers Arch... Doing a search on google archlinux hosting [1] I found some companies that I didn't notice of their existence in fact. Got a response from Slice: The following kernels are available for your slice to upgrade. Please let us know and we can take care of that for you. 2.6.24 - 23.48 2.6.24 - 24.55 I believe these should be Ubuntu kernel versions; I'm seeing right now what they actually include as it might include a fully working signalfd(). udev-145 should work fine with a 2.6.24.5 kernel or newer, and latest kernel above is definitely fixed: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.24.y.git;a=shortlog http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.24.y.git;a=commitdiff;h=c9c5091171cbf780bb293e6406dd8632b678bae8 https://launchpad.net/ubuntu/hardy/+source/linux/+changelog If anyone wants to contact some other providers (especially if you are already using their services) and post the response here, that would be cool. -Dan
Re: [arch-general] Bind 9.6.1-1 patched against dynamic update ddos?
On Wed, 2009-07-29 at 18:37 +0200, RedShift wrote: Fredrik Eriksson wrote: Hi, I've seen that there's a dynamic update ddos attack that is widely available on the net and after looking for the solution it seems that bind's latest patch (9.6.1-P1) solves this problem. So my question is more like this, is extra/bind 9.6.1-1 in the repository the same as bind 9.6.1-P1? The build date of the current package in extra/ says the 18 July but the homepage of BIND says the latest patch was published the 28 July. Best regards Fredrik Eriksson According to a commenter on the slashdot news article about this issue, this should provide a temporary countermeasure: iptables -A INPUT -p udp --dport 53 -j DROP -m u32 --u32 '30270xF=5' haven't tested it myself though... The current version 9.6.1.P1-1 in extra corrects the issue. k Glenn -- K. Piche kpi...@rogers.com