From: Dariush Pietrzak (eyck_at_ghost.anime.pl)
Date: Sun 23 Nov 2003 - 20:12:04 GMT
Hi hi,
remember old proftpd problem? The one you told me to create simple
test?
Here's another sympthom:
2003/11/23 20:28:45| commBind: Cannot bind socket FD 275 to 10.1.0.1:0:
(99) Cannot assign requested address
2003/11/23 20:31:45| commBind: Cannot bind socket FD 218 to 10.1.0.1:0:
(99) Cannot assign requested address
2003/11/23 20:32:29| commBind: Cannot bind socket FD 58 to 10.1.0.1:0: (99)
Cannot assign requested address
2003/11/23 20:34:45| commBind: Cannot bind socket FD 66 to 10.1.0.1:0: (99)
Cannot assign requested address
2003/11/23 20:36:11| commBind: Cannot bind socket FD 64 to 10.1.0.1:0: (99)
Cannot assign requested address
2003/11/23 20:36:11| commBind: Cannot bind socket FD 64 to 10.1.0.1:0: (99)
Cannot assign requested address
2003/11/23 20:36:16| commBind: Cannot bind socket FD 55 to 10.1.0.1:0: (99)
Cannot assign requested address
2003/11/23 20:36:29| commBind: Cannot bind socket FD 156 to 10.1.0.1:0:
(99) Cannot assign requested address
2003/11/23 20:36:32| commBind: Cannot bind socket FD 156 to 10.1.0.1:0:
(99) Cannot assign requested address
2003/11/23 20:36:35| commBind: Cannot bind socket FD 182 to 10.1.0.1:0:
(99) Cannot assign requested address
2003/11/23 20:36:35| commBind: Cannot bind socket FD 183 to 10.1.0.1:0:
(99) Cannot assign requested address
2003/11/23 20:36:39| commBind: Cannot bind socket FD 32 to 10.1.0.1:0: (99)
Cannot assign requested address
2003/11/23 20:36:42| commBind: Cannot bind socket FD 127 to 10.1.0.1:0:
(99) Cannot assign requested address
2003/11/23 20:36:45| commBind: Cannot bind socket FD 127 to 10.1.0.1:0:
(99) Cannot assign requested address
2003/11/23 20:36:45| commBind: Cannot bind socket FD 127 to 10.1.0.1:0:
(99) Cannot assign requested address
2003/11/23 20:37:08| commBind: Cannot bind socket FD 184 to 10.1.0.1:0:
(99) Cannot assign requested address
2003/11/23 20:37:20| commBind: Cannot bind socket FD 166 to 10.1.0.1:0:
(99) Cannot assign requested address
Anyone outthere thinking about running busy squid cache inside vserver:
think again. At least with old vserver, haven't tested new-style yet.
( and probably won't too soon in this environment, busy servers don't like
their kernels changed )
-- Key fingerprint = 40D0 9FFB 9939 7320 8294 05E0 BCC7 02C4 75CC 50D9 Namagumi namagomi namagoroshi _______________________________________________ Vserver mailing list Vserver_at_list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver