[Vserver] NFS problem

2004-10-16 Thread Robert Cope 
Hello,

This may have been covered before, but I haven't found it searching
Google, etc. And this may not even be a vserver problem, though I've
certainly done this other places without a problem.

What I've got is a vserver that needs to mount a few NFS shares. The
vserver has two IP addresses, a public and a private, on two network
interfaces. The NFS shares are mounted over the private network. The
problem is that the NFS server is getting the wrong IP sent to it (but
over the right interface), causing the the mount to fail.

The external IP is 172.17.19.114, internal is 172.17.20.114. You can see
that at some point in the conversation, the internal IP gets used, which
is wrong, since I'm only tcpdumping on the private interface. Here's TCP
output:

From client:

21:18:11.460901 172.17.20.114.836  172.17.20.21.sunrpc: S
1648716476:1648716476(0) win 5840 mss 1460,sackOK,timestamp 11931124
0,nop,wscale 0 (DF)
21:18:11.461060 172.17.20.21.sunrpc  172.17.20.114.836: S
1959198516:1959198516(0) ack 1648716477 win 5792 mss
1460,sackOK,timestamp 133480605 11931124,nop,wscale 0 (DF)
21:18:11.461071 172.17.20.114.836  172.17.20.21.sunrpc: . ack 1 win
5840 nop,nop,timestamp 11931125 133480605 (DF)
21:18:11.461102 172.17.20.114.836  172.17.20.21.sunrpc: P 1:45(44) ack
1 win 5840 nop,nop,timestamp 11931125 133480605 (DF)
21:18:11.461190 172.17.20.21.sunrpc  172.17.20.114.836: . ack 45 win
5792 nop,nop,timestamp 133480605 11931125 (DF)
21:18:11.461464 172.17.20.21.sunrpc  172.17.20.114.836: P 1:401(400)
ack 45 win 5792 nop,nop,timestamp 133480605 11931125 (DF)
21:18:11.461468 172.17.20.114.836  172.17.20.21.sunrpc: . ack 401 win
6432 nop,nop,timestamp 11931125 133480605 (DF)
21:18:11.461550 172.17.20.21.sunrpc  172.17.20.114.836: P 401:517(116)
ack 45 win 5792 nop,nop,timestamp 133480605 11931125 (DF)
21:18:11.461553 172.17.20.114.836  172.17.20.21.sunrpc: . ack 517 win
6432 nop,nop,timestamp 11931125 133480605 (DF)
21:18:11.461566 172.17.20.114.836  172.17.20.21.sunrpc: F 45:45(0) ack
517 win 6432 nop,nop,timestamp 11931125 133480605 (DF)
21:18:11.461613 172.17.19.114.837  172.17.20.21.32771:  udp 140 (DF)
21:18:11.461721 172.17.20.21.sunrpc  172.17.20.114.836: F 517:517(0)
ack 46 win 5792 nop,nop,timestamp 133480605 11931125 (DF)
21:18:11.461727 172.17.20.114.836  172.17.20.21.sunrpc: . ack 518 win
6432 nop,nop,timestamp 11931125 133480605 (DF)
21:18:11.610940 172.17.20.21.32771  172.17.19.114.837:  udp 28 (DF)
[ttl 0]

From server:
21:16:41.800374 172.17.20.114.836  labemsms-1i.messageone.com.sunrpc: S
1648716476:1648716476(0) win 5840 mss 1460,sackOK,timestamp 11931124
0,nop,wscale 0 (DF)
21:16:41.800396 labemsms-1i.messageone.com.sunrpc  172.17.20.114.836: S
1959198516:1959198516(0) ack 1648716477 win 5792 mss
1460,sackOK,timestamp 133480605 11931124,nop,wscale 0 (DF)
21:16:41.800500 172.17.20.114.836  labemsms-1i.messageone.com.sunrpc: .
ack 1 win 5840 nop,nop,timestamp 11931125 133480605 (DF)
21:16:41.800517 172.17.20.114.836  labemsms-1i.messageone.com.sunrpc: P
1:45(44) ack 1 win 5840 nop,nop,timestamp 11931125 133480605 (DF)
21:16:41.800524 labemsms-1i.messageone.com.sunrpc  172.17.20.114.836: .
ack 45 win 5792 nop,nop,timestamp 133480605 11931125 (DF)
21:16:41.800785 labemsms-1i.messageone.com.sunrpc  172.17.20.114.836: P
1:401(400) ack 45 win 5792 nop,nop,timestamp 133480605 11931125 (DF)
21:16:41.800876 172.17.20.114.836  labemsms-1i.messageone.com.sunrpc: .
ack 401 win 6432 nop,nop,timestamp 11931125 133480605 (DF)
21:16:41.800884 labemsms-1i.messageone.com.sunrpc  172.17.20.114.836: P
401:517(116) ack 45 win 5792 nop,nop,timestamp 133480605 11931125 (DF)
21:16:41.800999 172.17.20.114.836  labemsms-1i.messageone.com.sunrpc: .
ack 517 win 6432 nop,nop,timestamp 11931125 133480605 (DF)
21:16:41.801003 172.17.20.114.836  labemsms-1i.messageone.com.sunrpc: F
45:45(0) ack 517 win 6432 nop,nop,timestamp 11931125 133480605 (DF)
21:16:41.801009 172.17.19.114.837  labemsms-1i.messageone.com.32771:
udp 140 (DF)
21:16:41.801052 labemsms-1i.messageone.com.sunrpc  172.17.20.114.836: F
517:517(0) ack 46 win 5792 nop,nop,timestamp 133480605 11931125 (DF)
21:16:41.801126 172.17.20.114.836  labemsms-1i.messageone.com.sunrpc: .
ack 518 win 6432 nop,nop,timestamp 11931125 133480605 (DF)
21:16:41.950270 labemsms-1i.messageone.com.32771  172.17.19.114.837:
udp 28 (DF) [ttl 0]

Any thoughts would be appreciated,

robert
___
Vserver mailing list
[EMAIL PROTECTED]
http://list.linux-vserver.org/mailman/listinfo/vserver

RE: [Vserver] This Drug puts VlAGRA to shame!!

2004-07-09 Thread Robert Cope 
Herbert Poetzl wrote:

 On Fri, Jul 09, 2004 at 11:42:48AM +0200, Marc-Christian Petersen
 wrote: 
 On Friday 09 July 2004 11:35, alvaro wrote:
 
 Either make this list FINALLY subscribed ONLY or remove me. I can't
 read this spam any longer!
 
 martin, please remove marc ...

The funny part about this, IMHO, is that my spam filter catches all the
spam to this list. So if it wasn't for people crying about it, I
wouldn't even notice. And surely I can't be the only one in that boat.

I guess I could email Marc and talk to him about spam filters.

robert
___
Vserver mailing list
[EMAIL PROTECTED]
http://list.linux-vserver.org/mailman/listinfo/vserver

[Vserver] process accounting

2004-02-08 Thread Robert Cope 
Hello,

Hopefully I have not missed the obvious, but I am wondering if there is 
any way to get the BSD process accounting data per vserver. Thanks,

robert


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [Vserver] process accounting

2004-02-08 Thread Robert Cope 
Herbert Poetzl wrote:

On Sun, Feb 08, 2004 at 06:23:31PM -0600, Robert Cope wrote:

Hello,

Hopefully I have not missed the obvious, but I am wondering if there is 
any way to get the BSD process accounting data per vserver. Thanks,


hmm, as the name says, it's 'process accounting' so
that can't be simply 'extended' to an entire vserver ...
in what part are you interested, and how would you
expect such a feature to work, from a user perspective?
just to get an overview what BSD accounting contains:

 __u16ac_uid; /* Accounting Real User ID */
 __u16ac_gid; /* Accounting Real Group ID */
 __u16ac_tty; /* Accounting Control Terminal */
 __u32ac_btime;   /* Accounting Process Creation Time */
 comp_t   ac_utime;   /* Accounting User Time */
 comp_t   ac_stime;   /* Accounting System Time */
 comp_t   ac_etime;   /* Accounting Elapsed Time */
 comp_t   ac_mem; /* Accounting Average Memory Usage */
 comp_t   ac_io;  /* Accounting Chars Transferred */
 comp_t   ac_rw;  /* Accounting Blocks Read or Written */
 comp_t   ac_minflt;  /* Accounting Minor Pagefaults */
 comp_t   ac_majflt;  /* Accounting Major Pagefaults */
 comp_t   ac_swaps;   /* Accounting Number of Swaps */
 __u32ac_exitcode;/* Accounting Exitcode */
 char ac_comm[ACCT_COMM + 1]; /* Accounting Command Name */
 char ac_pad[10]; /* Accounting Padding Bytes */
Thanks, I've been looking at this since asking the question -- use the 
source, Luke, and all that.

What I'd like is for the proccess accounting system to store the context 
ID. In that way, for example, with 'lastcomm' (on the host), I would 
know in which context a command was run. Does that make sense?

I'm going to look into what it would take to add this functionality to 
the kernel and to the acct tools.

Thanks,

robert

robert



smime.p7s
Description: S/MIME Cryptographic Signature