Debian - Odd, hopefully minor, machine name / prompt issue
Hi All... I just upgraded the kernel on my machine from: actual:/home/jim/openvz/kernels# uname -a Linux actual.registrationtek.com 2.6.18-openvz-12-1etch1-amd64 #1 SMP Fri May 4 23:37:24 MSD 2007 x86_64 GNU/Linux To: vps5000:~# uname -a Linux vps5000.regtek.com 2.6.18-openvz-13-39.1d1-amd64 #1 SMP Mon Sep 3 10:11:00 MSD 2007 x86_64 GNU/Linux I did this because I have been having a memory consumption problem with Exim4 I was hoping to resolve. I had been told that the Exim4 memory issue was a known issue and was fixed in later kernels. Anyhow, I installed the new kernel using dpkg -i and it seems to install fine, with no warnings or errors. It boots and runs fine, even iSCSI. But, the odd issue is that the machine name in the prompt is wrong. As you can see from above, it went from: actual# To: vps5000# The name of the machine in /etc/hostname is actual and vps5000 is the highest number vps I have. Is this a serious issue or can I safely ignore it? Thanks... Jim
Re: Debian - Odd, hopefully minor, machine name / prompt issue
Jim, Can you run hostname on the host system and inside a couple of VEs? Do they show the same or different hostnames? Jim Archer wrote: > Hi All... > > I just upgraded the kernel on my machine from: > > actual:/home/jim/openvz/kernels# uname -a > Linux actual.registrationtek.com 2.6.18-openvz-12-1etch1-amd64 #1 SMP > Fri May 4 23:37:24 MSD 2007 x86_64 GNU/Linux > > To: > > vps5000:~# uname -a > Linux vps5000.regtek.com 2.6.18-openvz-13-39.1d1-amd64 #1 SMP Mon Sep > 3 10:11:00 MSD 2007 x86_64 GNU/Linux > > > I did this because I have been having a memory consumption problem > with Exim4 I was hoping to resolve. I had been told that the Exim4 > memory issue was a known issue and was fixed in later kernels. > > Anyhow, I installed the new kernel using dpkg -i and it seems to > install fine, with no warnings or errors. It boots and runs fine, > even iSCSI. But, the odd issue is that the machine name in the prompt > is wrong. As you can see from above, it went from: > > actual# > > To: > > vps5000# > > The name of the machine in /etc/hostname is actual and vps5000 is the > highest number vps I have. Is this a serious issue or can I safely > ignore it? > > Thanks... > > Jim >
When logged into the main system: vps5000:~# hostname vps5000.regtek.com vps5000:~# vzlist VEID NPROC STATUS IP_ADDR HOSTNAME 102 13 running 72.46.65.30 nsp4.registrationtek.com 104 21 running 72.46.65.47 mail5.registrationtek.com 105 22 running 72.46.65.48 whois.registrationtek.com 106 4 running 72.46.65.54 gz.registrationtek.com 107 7 running 72.46.65.34 squid.registrationtek.com 1000 4 running 72.46.67.2 vps1000.regtek.com 1001 39 running 72.46.67.3 vps1002.registrationtek.com 1002 29 running 72.46.67.7 tocco.regtek.com 1003 23 running 72.46.67.8 firstclass.regtek.com 5000 4 running 72.46.65.254 vps5000.regtek.com vps5000:~# vzctl enter 102 entered into VE 102 vps5000:/# hostname vps5000.regtek.com vps5000:/# exit logout exited from VE 102 vps5000:~# vzctl enter 104 entered into VE 104 vps5000:/# hostname vps5000.regtek.com vps5000:/# exit logout exited from VE 104 vps5000:~# vzctl enter 1003 entered into VE 1003 vps5000:/# hostname vps5000.regtek.com vps5000:/# exit logout exited from VE 1003 vps5000:~# --On Wednesday, September 12, 2007 1:30 PM +0400 Kir Kolyshkin <kir@openvz.org> wrote: > Jim, > > Can you run hostname on the host system and inside a couple of VEs? Do > they show the same or different hostnames? > > Jim Archer wrote: >> Hi All... >> >> I just upgraded the kernel on my machine from: >> >> actual:/home/jim/openvz/kernels# uname -a >> Linux actual.registrationtek.com 2.6.18-openvz-12-1etch1-amd64 #1 SMP >> Fri May 4 23:37:24 MSD 2007 x86_64 GNU/Linux >> >> To: >> >> vps5000:~# uname -a >> Linux vps5000.regtek.com 2.6.18-openvz-13-39.1d1-amd64 #1 SMP Mon Sep >> 3 10:11:00 MSD 2007 x86_64 GNU/Linux >> >> >> I did this because I have been having a memory consumption problem >> with Exim4 I was hoping to resolve. I had been told that the Exim4 >> memory issue was a known issue and was fixed in later kernels. >> >> Anyhow, I installed the new kernel using dpkg -i and it seems to >> install fine, with no warnings or errors. It boots and runs fine, >> even iSCSI. But, the odd issue is that the machine name in the prompt >> is wrong. As you can see from above, it went from: >> >> actual# >> >> To: >> >> vps5000# >> >> The name of the machine in /etc/hostname is actual and vps5000 is the >> highest number vps I have. Is this a serious issue or can I safely >> ignore it? >> >> Thanks... >> >> Jim >>
Thanks for reporting. Apparently when porting OpenVZ patchset to debian kernel utsname() virtualization got screwed... I suggest you to file a bug to http://bugs.debian.org/, and I have added Debian maintainer of OpenVZ packages to cc. Jim Archer wrote: > When logged into the main system: > > vps5000:~# hostname > vps5000.regtek.com > vps5000:~# vzlist > VEID NPROC STATUS IP_ADDR HOSTNAME > 102 13 running 72.46.65.30 nsp4.registrationtek.com > 104 21 running 72.46.65.47 mail5.registrationtek.com > 105 22 running 72.46.65.48 whois.registrationtek.com > 106 4 running 72.46.65.54 gz.registrationtek.com > 107 7 running 72.46.65.34 squid.registrationtek.com > 1000 4 running 72.46.67.2 vps1000.regtek.com > 1001 39 running 72.46.67.3 vps1002.registrationtek.com > 1002 29 running 72.46.67.7 tocco.regtek.com > 1003 23 running 72.46.67.8 firstclass.regtek.com > 5000 4 running 72.46.65.254 vps5000.regtek.com > vps5000:~# vzctl enter 102 > entered into VE 102 > vps5000:/# hostname > vps5000.regtek.com > vps5000:/# exit > logout > exited from VE 102 > vps5000:~# vzctl enter 104 > entered into VE 104 > vps5000:/# hostname > vps5000.regtek.com > vps5000:/# exit > logout > exited from VE 104 > vps5000:~# vzctl enter 1003 > entered into VE 1003 > vps5000:/# hostname > vps5000.regtek.com > vps5000:/# exit > logout > exited from VE 1003 > vps5000:~# > > > > > --On Wednesday, September 12, 2007 1:30 PM +0400 Kir Kolyshkin > <kir@openvz.org> wrote: > >> Jim, >> >> Can you run hostname on the host system and inside a couple of VEs? Do >> they show the same or different hostnames? >> >> Jim Archer wrote: >>> Hi All... >>> >>> I just upgraded the kernel on my machine from: >>> >>> actual:/home/jim/openvz/kernels# uname -a >>> Linux actual.registrationtek.com 2.6.18-openvz-12-1etch1-amd64 #1 SMP >>> Fri May 4 23:37:24 MSD 2007 x86_64 GNU/Linux >>> >>> To: >>> >>> vps5000:~# uname -a >>> Linux vps5000.regtek.com 2.6.18-openvz-13-39.1d1-amd64 #1 SMP Mon Sep >>> 3 10:11:00 MSD 2007 x86_64 GNU/Linux >>> >>> >>> I did this because I have been having a memory consumption problem >>> with Exim4 I was hoping to resolve. I had been told that the Exim4 >>> memory issue was a known issue and was fixed in later kernels. >>> >>> Anyhow, I installed the new kernel using dpkg -i and it seems to >>> install fine, with no warnings or errors. It boots and runs fine, >>> even iSCSI. But, the odd issue is that the machine name in the prompt >>> is wrong. As you can see from above, it went from: >>> >>> actual# >>> >>> To: >>> >>> vps5000# >>> >>> The name of the machine in /etc/hostname is actual and vps5000 is the >>> highest number vps I have. Is this a serious issue or can I safely >>> ignore it? >>> >>> Thanks... >>> >>> Jim >>>
Okay, I'll file the bug report tonight. Is there a reason I should stop using this kernel, or is this a minor issue? --On Thursday, September 13, 2007 12:55 AM +0400 Kir Kolyshkin <kir@openvz.org> wrote: > Thanks for reporting. Apparently when porting OpenVZ patchset to debian > kernel utsname() virtualization got screwed... I suggest you to file a > bug to http://bugs.debian.org/, and I have added Debian maintainer of > OpenVZ packages to cc. > > Jim Archer wrote: >> When logged into the main system: >> >> vps5000:~# hostname >> vps5000.regtek.com >> vps5000:~# vzlist >> VEID NPROC STATUS IP_ADDR HOSTNAME >> 102 13 running 72.46.65.30 nsp4.registrationtek.com >> 104 21 running 72.46.65.47 mail5.registrationtek.com >> 105 22 running 72.46.65.48 whois.registrationtek.com >> 106 4 running 72.46.65.54 gz.registrationtek.com >> 107 7 running 72.46.65.34 squid.registrationtek.com >> 1000 4 running 72.46.67.2 vps1000.regtek.com >> 1001 39 running 72.46.67.3 vps1002.registrationtek.com >> 1002 29 running 72.46.67.7 tocco.regtek.com >> 1003 23 running 72.46.67.8 firstclass.regtek.com >> 5000 4 running 72.46.65.254 vps5000.regtek.com >> vps5000:~# vzctl enter 102 >> entered into VE 102 >> vps5000:/# hostname >> vps5000.regtek.com >> vps5000:/# exit >> logout >> exited from VE 102 >> vps5000:~# vzctl enter 104 >> entered into VE 104 >> vps5000:/# hostname >> vps5000.regtek.com >> vps5000:/# exit >> logout >> exited from VE 104 >> vps5000:~# vzctl enter 1003 >> entered into VE 1003 >> vps5000:/# hostname >> vps5000.regtek.com >> vps5000:/# exit >> logout >> exited from VE 1003 >> vps5000:~# >> >> >> >> >> --On Wednesday, September 12, 2007 1:30 PM +0400 Kir Kolyshkin >> <kir@openvz.org> wrote: >> >>> Jim, >>> >>> Can you run hostname on the host system and inside a couple of VEs? Do >>> they show the same or different hostnames? >>> >>> Jim Archer wrote: >>>> Hi All... >>>> >>>> I just upgraded the kernel on my machine from: >>>> >>>> actual:/home/jim/openvz/kernels# uname -a >>>> Linux actual.registrationtek.com 2.6.18-openvz-12-1etch1-amd64 #1 SMP >>>> Fri May 4 23:37:24 MSD 2007 x86_64 GNU/Linux >>>> >>>> To: >>>> >>>> vps5000:~# uname -a >>>> Linux vps5000.regtek.com 2.6.18-openvz-13-39.1d1-amd64 #1 SMP Mon Sep >>>> 3 10:11:00 MSD 2007 x86_64 GNU/Linux >>>> >>>> >>>> I did this because I have been having a memory consumption problem >>>> with Exim4 I was hoping to resolve. I had been told that the Exim4 >>>> memory issue was a known issue and was fixed in later kernels. >>>> >>>> Anyhow, I installed the new kernel using dpkg -i and it seems to >>>> install fine, with no warnings or errors. It boots and runs fine, >>>> even iSCSI. But, the odd issue is that the machine name in the prompt >>>> is wrong. As you can see from above, it went from: >>>> >>>> actual# >>>> >>>> To: >>>> >>>> vps5000# >>>> >>>> The name of the machine in /etc/hostname is actual and vps5000 is the >>>> highest number vps I have. Is this a serious issue or can I safely >>>> ignore it? >>>> >>>> Thanks... >>>> >>>> Jim >>>>
Hi Jim That depends on what you have on the system. In some cases the configuration is dependent on the hostname. For example exim can get a bit confused if the hostname is not the correct one. I will start to look on this bug asap. As Kir said something must have become wrong when the patchset was merged to Debian. Best regards, // Ola On Wed, Sep 12, 2007 at 04:59:33PM -0400, Jim Archer wrote: > Okay, I'll file the bug report tonight. Is there a reason I should stop > using this kernel, or is this a minor issue? > > --On Thursday, September 13, 2007 12:55 AM +0400 Kir Kolyshkin > <kir@openvz.org> wrote: > > >Thanks for reporting. Apparently when porting OpenVZ patchset to debian > >kernel utsname() virtualization got screwed... I suggest you to file a > >bug to http://bugs.debian.org/, and I have added Debian maintainer of > >OpenVZ packages to cc. > > > >Jim Archer wrote: > >>When logged into the main system: > >> > >>vps5000:~# hostname > >>vps5000.regtek.com > >>vps5000:~# vzlist > >> VEID NPROC STATUS IP_ADDR HOSTNAME > >> 102 13 running 72.46.65.30 nsp4.registrationtek.com > >> 104 21 running 72.46.65.47 mail5.registrationtek.com > >> 105 22 running 72.46.65.48 whois.registrationtek.com > >> 106 4 running 72.46.65.54 gz.registrationtek.com > >> 107 7 running 72.46.65.34 squid.registrationtek.com > >> 1000 4 running 72.46.67.2 vps1000.regtek.com > >> 1001 39 running 72.46.67.3 vps1002.registrationtek.com > >> 1002 29 running 72.46.67.7 tocco.regtek.com > >> 1003 23 running 72.46.67.8 firstclass.regtek.com > >> 5000 4 running 72.46.65.254 vps5000.regtek.com > >>vps5000:~# vzctl enter 102 > >>entered into VE 102 > >>vps5000:/# hostname > >>vps5000.regtek.com > >>vps5000:/# exit > >>logout > >>exited from VE 102 > >>vps5000:~# vzctl enter 104 > >>entered into VE 104 > >>vps5000:/# hostname > >>vps5000.regtek.com > >>vps5000:/# exit > >>logout > >>exited from VE 104 > >>vps5000:~# vzctl enter 1003 > >>entered into VE 1003 > >>vps5000:/# hostname > >>vps5000.regtek.com > >>vps5000:/# exit > >>logout > >>exited from VE 1003 > >>vps5000:~# > >> > >> > >> > >> > >>--On Wednesday, September 12, 2007 1:30 PM +0400 Kir Kolyshkin > >><kir@openvz.org> wrote: > >> > >>>Jim, > >>> > >>>Can you run hostname on the host system and inside a couple of VEs? Do > >>>they show the same or different hostnames? > >>> > >>>Jim Archer wrote: > >>>>Hi All... > >>>> > >>>>I just upgraded the kernel on my machine from: > >>>> > >>>>actual:/home/jim/openvz/kernels# uname -a > >>>>Linux actual.registrationtek.com 2.6.18-openvz-12-1etch1-amd64 #1 SMP > >>>>Fri May 4 23:37:24 MSD 2007 x86_64 GNU/Linux > >>>> > >>>>To: > >>>> > >>>>vps5000:~# uname -a > >>>>Linux vps5000.regtek.com 2.6.18-openvz-13-39.1d1-amd64 #1 SMP Mon Sep > >>>>3 10:11:00 MSD 2007 x86_64 GNU/Linux > >>>> > >>>> > >>>>I did this because I have been having a memory consumption problem > >>>>with Exim4 I was hoping to resolve. I had been told that the Exim4 > >>>>memory issue was a known issue and was fixed in later kernels. > >>>> > >>>>Anyhow, I installed the new kernel using dpkg -i and it seems to > >>>>install fine, with no warnings or errors. It boots and runs fine, > >>>>even iSCSI. But, the odd issue is that the machine name in the prompt > >>>>is wrong. As you can see from above, it went from: > >>>> > >>>>actual# > >>>> > >>>>To: > >>>> > >>>>vps5000# > >>>> > >>>>The name of the machine in /etc/hostname is actual and vps5000 is the > >>>>highest number vps I have. Is this a serious issue or can I safely > >>>>ignore it? > >>>> > >>>>Thanks... > >>>> > >>>>Jim > >>>> -- --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering ---- / ola@opalsys.net Annebergsslingan 37 \ | opal@debian.org 654 65 KARLSTAD | | http://opalsys.net/ Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / ---------------------------------------------------------------
Thanks very much Ola. What package do you want the bug reported against? --On Thursday, September 13, 2007 7:07 AM +0200 Ola Lundqvist <ola@opalsys.net> wrote: > Hi Jim > > That depends on what you have on the system. In some cases the > configuration is dependent on the hostname. For example exim can get a > bit confused if the hostname is not the correct one. > > I will start to look on this bug asap. As Kir said something must have > become wrong when the patchset was merged to Debian. > > Best regards, > > // Ola > > On Wed, Sep 12, 2007 at 04:59:33PM -0400, Jim Archer wrote: >> Okay, I'll file the bug report tonight. Is there a reason I should stop >> using this kernel, or is this a minor issue? >> >> --On Thursday, September 13, 2007 12:55 AM +0400 Kir Kolyshkin >> <kir@openvz.org> wrote: >> >> > Thanks for reporting. Apparently when porting OpenVZ patchset to debian >> > kernel utsname() virtualization got screwed... I suggest you to file a >> > bug to http://bugs.debian.org/, and I have added Debian maintainer of >> > OpenVZ packages to cc. >> > >> > Jim Archer wrote: >> >> When logged into the main system: >> >> >> >> vps5000:~# hostname >> >> vps5000.regtek.com >> >> vps5000:~# vzlist >> >> VEID NPROC STATUS IP_ADDR HOSTNAME >> >> 102 13 running 72.46.65.30 nsp4.registrationtek.com >> >> 104 21 running 72.46.65.47 mail5.registrationtek.com >> >> 105 22 running 72.46.65.48 whois.registrationtek.com >> >> 106 4 running 72.46.65.54 gz.registrationtek.com >> >> 107 7 running 72.46.65.34 squid.registrationtek.com >> >> 1000 4 running 72.46.67.2 vps1000.regtek.com >> >> 1001 39 running 72.46.67.3 >> >> vps1002.registrationtek.com 1002 29 running 72.46.67.7 >> >> tocco.regtek.com 1003 23 running 72.46.67.8 >> >> firstclass.regtek.com 5000 4 running 72.46.65.254 >> >> vps5000.regtek.com >> >> vps5000:~# vzctl enter 102 >> >> entered into VE 102 >> >> vps5000:/# hostname >> >> vps5000.regtek.com >> >> vps5000:/# exit >> >> logout >> >> exited from VE 102 >> >> vps5000:~# vzctl enter 104 >> >> entered into VE 104 >> >> vps5000:/# hostname >> >> vps5000.regtek.com >> >> vps5000:/# exit >> >> logout >> >> exited from VE 104 >> >> vps5000:~# vzctl enter 1003 >> >> entered into VE 1003 >> >> vps5000:/# hostname >> >> vps5000.regtek.com >> >> vps5000:/# exit >> >> logout >> >> exited from VE 1003 >> >> vps5000:~# >> >> >> >> >> >> >> >> >> >> --On Wednesday, September 12, 2007 1:30 PM +0400 Kir Kolyshkin >> >> <kir@openvz.org> wrote: >> >> >> >>> Jim, >> >>> >> >>> Can you run hostname on the host system and inside a couple of VEs? >> >>> Do they show the same or different hostnames? >> >>> >> >>> Jim Archer wrote: >> >>>> Hi All... >> >>>> >> >>>> I just upgraded the kernel on my machine from: >> >>>> >> >>>> actual:/home/jim/openvz/kernels# uname -a >> >>>> Linux actual.registrationtek.com 2.6.18-openvz-12-1etch1-amd64 #1 >> >>>> SMP Fri May 4 23:37:24 MSD 2007 x86_64 GNU/Linux >> >>>> >> >>>> To: >> >>>> >> >>>> vps5000:~# uname -a >> >>>> Linux vps5000.regtek.com 2.6.18-openvz-13-39.1d1-amd64 #1 SMP Mon >> >>>> Sep 3 10:11:00 MSD 2007 x86_64 GNU/Linux >> >>>> >> >>>> >> >>>> I did this because I have been having a memory consumption problem >> >>>> with Exim4 I was hoping to resolve. I had been told that the Exim4 >> >>>> memory issue was a known issue and was fixed in later kernels. >> >>>> >> >>>> Anyhow, I installed the new kernel using dpkg -i and it seems to >> >>>> install fine, with no warnings or errors. It boots and runs fine, >> >>>> even iSCSI. But, the odd issue is that the machine name in the >> >>>> prompt is wrong. As you can see from above, it went from: >> >>>> >> >>>> actual# >> >>>> >> >>>> To: >> >>>> >> >>>> vps5000# >> >>>> >> >>>> The name of the machine in /etc/hostname is actual and vps5000 is >> >>>> the highest number vps I have. Is this a serious issue or can I >> >>>> safely ignore it? >> >>>> >> >>>> Thanks... >> >>>> >> >>>> Jim >> >>>> > -- > --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering ---- > / ola@opalsys.net Annebergsslingan 37 \ >| opal@debian.org 654 65 KARLSTAD | >| http://opalsys.net/ Mobile: +46 (0)70-332 1551 | > \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / > ---------------------------------------------------------------
Hi kernel-patch-openvz Best regards, // Ola On Thu, Sep 13, 2007 at 02:12:19AM -0400, Jim Archer wrote: > Thanks very much Ola. What package do you want the bug reported against? > > > --On Thursday, September 13, 2007 7:07 AM +0200 Ola Lundqvist > <ola@opalsys.net> wrote: > > >Hi Jim > > > >That depends on what you have on the system. In some cases the > >configuration is dependent on the hostname. For example exim can get a > >bit confused if the hostname is not the correct one. > > > >I will start to look on this bug asap. As Kir said something must have > >become wrong when the patchset was merged to Debian. > > > >Best regards, > > > >// Ola > > > >On Wed, Sep 12, 2007 at 04:59:33PM -0400, Jim Archer wrote: > >>Okay, I'll file the bug report tonight. Is there a reason I should stop > >>using this kernel, or is this a minor issue? > >> > >>--On Thursday, September 13, 2007 12:55 AM +0400 Kir Kolyshkin > >><kir@openvz.org> wrote: > >> > >>> Thanks for reporting. Apparently when porting OpenVZ patchset to debian > >>> kernel utsname() virtualization got screwed... I suggest you to file a > >>> bug to http://bugs.debian.org/, and I have added Debian maintainer of > >>> OpenVZ packages to cc. > >>> > >>> Jim Archer wrote: > >>>> When logged into the main system: > >>>> > >>>> vps5000:~# hostname > >>>> vps5000.regtek.com > >>>> vps5000:~# vzlist > >>>> VEID NPROC STATUS IP_ADDR HOSTNAME > >>>> 102 13 running 72.46.65.30 nsp4.registrationtek.com > >>>> 104 21 running 72.46.65.47 mail5.registrationtek.com > >>>> 105 22 running 72.46.65.48 whois.registrationtek.com > >>>> 106 4 running 72.46.65.54 gz.registrationtek.com > >>>> 107 7 running 72.46.65.34 squid.registrationtek.com > >>>> 1000 4 running 72.46.67.2 vps1000.regtek.com > >>>> 1001 39 running 72.46.67.3 > >>>> vps1002.registrationtek.com 1002 29 running 72.46.67.7 > >>>> tocco.regtek.com 1003 23 running 72.46.67.8 > >>>> firstclass.regtek.com 5000 4 running 72.46.65.254 > >>>> vps5000.regtek.com > >>>> vps5000:~# vzctl enter 102 > >>>> entered into VE 102 > >>>> vps5000:/# hostname > >>>> vps5000.regtek.com > >>>> vps5000:/# exit > >>>> logout > >>>> exited from VE 102 > >>>> vps5000:~# vzctl enter 104 > >>>> entered into VE 104 > >>>> vps5000:/# hostname > >>>> vps5000.regtek.com > >>>> vps5000:/# exit > >>>> logout > >>>> exited from VE 104 > >>>> vps5000:~# vzctl enter 1003 > >>>> entered into VE 1003 > >>>> vps5000:/# hostname > >>>> vps5000.regtek.com > >>>> vps5000:/# exit > >>>> logout > >>>> exited from VE 1003 > >>>> vps5000:~# > >>>> > >>>> > >>>> > >>>> > >>>> --On Wednesday, September 12, 2007 1:30 PM +0400 Kir Kolyshkin > >>>> <kir@openvz.org> wrote: > >>>> > >>>>> Jim, > >>>>> > >>>>> Can you run hostname on the host system and inside a couple of VEs? > >>>>> Do they show the same or different hostnames? > >>>>> > >>>>> Jim Archer wrote: > >>>>>> Hi All... > >>>>>> > >>>>>> I just upgraded the kernel on my machine from: > >>>>>> > >>>>>> actual:/home/jim/openvz/kernels# uname -a > >>>>>> Linux actual.registrationtek.com 2.6.18-openvz-12-1etch1-amd64 #1 > >>>>>> SMP Fri May 4 23:37:24 MSD 2007 x86_64 GNU/Linux > >>>>>> > >>>>>> To: > >>>>>> > >>>>>> vps5000:~# uname -a > >>>>>> Linux vps5000.regtek.com 2.6.18-openvz-13-39.1d1-amd64 #1 SMP Mon > >>>>>> Sep 3 10:11:00 MSD 2007 x86_64 GNU/Linux > >>>>>> > >>>>>> > >>>>>> I did this because I have been having a memory consumption problem > >>>>>> with Exim4 I was hoping to resolve. I had been told that the Exim4 > >>>>>> memory issue was a known issue and was fixed in later kernels. > >>>>>> > >>>>>> Anyhow, I installed the new kernel using dpkg -i and it seems to > >>>>>> install fine, with no warnings or errors. It boots and runs fine, > >>>>>> even iSCSI. But, the odd issue is that the machine name in the > >>>>>> prompt is wrong. As you can see from above, it went from: > >>>>>> > >>>>>> actual# > >>>>>> > >>>>>> To: > >>>>>> > >>>>>> vps5000# > >>>>>> > >>>>>> The name of the machine in /etc/hostname is actual and vps5000 is > >>>>>> the highest number vps I have. Is this a serious issue or can I > >>>>>> safely ignore it? > >>>>>> > >>>>>> Thanks... > >>>>>> > >>>>>> Jim > >>>>>> > >-- > > --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering ---- > >/ ola@opalsys.net Annebergsslingan 37 \ > >| opal@debian.org 654 65 KARLSTAD | > >| http://opalsys.net/ Mobile: +46 (0)70-332 1551 | > >\ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / > > --------------------------------------------------------------- > > > > > -- --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering ---- / ola@opalsys.net Annebergsslingan 37 \ | opal@debian.org 654 65 KARLSTAD | | http://opalsys.net/ Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / ---------------------------------------------------------------
Hi Ola... As embarrassing as this is, I have to admit that I can't figure out how to open a bug report using the link provided below. That's why the report is not filed yet. Also, I experienced a kernel panic with this kernel. Another engineer restarted the system, but because he was accessing via an IPMI card (so no text console) he was unable to copy out the associated information from the kernel. If there is something I can get you from the machine, I'll be happy to do so. Also, another person I know knows how to open Debian bug reports, but he won't be available until after the Jewish holiday. As soon as I can talk with him I'll open the bug. --On Thursday, September 13, 2007 9:19 AM +0200 Ola Lundqvist <ola@opalsys.net> wrote: > Hi > > kernel-patch-openvz > > Best regards, > > // Ola > > On Thu, Sep 13, 2007 at 02:12:19AM -0400, Jim Archer wrote: >> Thanks very much Ola. What package do you want the bug reported against? >> >> >> --On Thursday, September 13, 2007 7:07 AM +0200 Ola Lundqvist >> <ola@opalsys.net> wrote: >> >> > Hi Jim >> > >> > That depends on what you have on the system. In some cases the >> > configuration is dependent on the hostname. For example exim can get a >> > bit confused if the hostname is not the correct one. >> > >> > I will start to look on this bug asap. As Kir said something must have >> > become wrong when the patchset was merged to Debian. >> > >> > Best regards, >> > >> > // Ola >> > >> > On Wed, Sep 12, 2007 at 04:59:33PM -0400, Jim Archer wrote: >> >> Okay, I'll file the bug report tonight. Is there a reason I should >> >> stop using this kernel, or is this a minor issue? >> >> >> >> --On Thursday, September 13, 2007 12:55 AM +0400 Kir Kolyshkin >> >> <kir@openvz.org> wrote: >> >> >> >>> Thanks for reporting. Apparently when porting OpenVZ patchset to >> >>> debian kernel utsname() virtualization got screwed... I suggest you >> >>> to file a bug to http://bugs.debian.org/, and I have added Debian >> >>> maintainer of OpenVZ packages to cc. >> >>> >> >>> Jim Archer wrote: >> >>>> When logged into the main system: >> >>>> >> >>>> vps5000:~# hostname >> >>>> vps5000.regtek.com >> >>>> vps5000:~# vzlist >> >>>> VEID NPROC STATUS IP_ADDR HOSTNAME >> >>>> 102 13 running 72.46.65.30 nsp4.registrationtek.com >> >>>> 104 21 running 72.46.65.47 >> >>>> mail5.registrationtek.com 105 22 running 72.46.65.48 >> >>>> whois.registrationtek.com 106 4 running 72.46.65.54 >> >>>> gz.registrationtek.com 107 7 running 72.46.65.34 >> >>>> squid.registrationtek.com 1000 4 running 72.46.67.2 >> >>>> vps1000.regtek.com 1001 39 running 72.46.67.3 >> >>>> vps1002.registrationtek.com 1002 29 running 72.46.67.7 >> >>>> tocco.regtek.com 1003 23 running 72.46.67.8 >> >>>> firstclass.regtek.com 5000 4 running 72.46.65.254 >> >>>> vps5000.regtek.com >> >>>> vps5000:~# vzctl enter 102 >> >>>> entered into VE 102 >> >>>> vps5000:/# hostname >> >>>> vps5000.regtek.com >> >>>> vps5000:/# exit >> >>>> logout >> >>>> exited from VE 102 >> >>>> vps5000:~# vzctl enter 104 >> >>>> entered into VE 104 >> >>>> vps5000:/# hostname >> >>>> vps5000.regtek.com >> >>>> vps5000:/# exit >> >>>> logout >> >>>> exited from VE 104 >> >>>> vps5000:~# vzctl enter 1003 >> >>>> entered into VE 1003 >> >>>> vps5000:/# hostname >> >>>> vps5000.regtek.com >> >>>> vps5000:/# exit >> >>>> logout >> >>>> exited from VE 1003 >> >>>> vps5000:~# >> >>>> >> >>>> >> >>>> >> >>>> >> >>>> --On Wednesday, September 12, 2007 1:30 PM +0400 Kir Kolyshkin >> >>>> <kir@openvz.org> wrote: >> >>>> >> >>>>> Jim, >> >>>>> >> >>>>> Can you run hostname on the host system and inside a couple of VEs? >> >>>>> Do they show the same or different hostnames? >> >>>>> >> >>>>> Jim Archer wrote: >> >>>>>> Hi All... >> >>>>>> >> >>>>>> I just upgraded the kernel on my machine from: >> >>>>>> >> >>>>>> actual:/home/jim/openvz/kernels# uname -a >> >>>>>> Linux actual.registrationtek.com 2.6.18-openvz-12-1etch1-amd64 #1 >> >>>>>> SMP Fri May 4 23:37:24 MSD 2007 x86_64 GNU/Linux >> >>>>>> >> >>>>>> To: >> >>>>>> >> >>>>>> vps5000:~# uname -a >> >>>>>> Linux vps5000.regtek.com 2.6.18-openvz-13-39.1d1-amd64 #1 SMP Mon >> >>>>>> Sep 3 10:11:00 MSD 2007 x86_64 GNU/Linux >> >>>>>> >> >>>>>> >> >>>>>> I did this because I have been having a memory consumption problem >> >>>>>> with Exim4 I was hoping to resolve. I had been told that the >> >>>>>> Exim4 memory issue was a known issue and was fixed in later >> >>>>>> kernels. >> >>>>>> >> >>>>>> Anyhow, I installed the new kernel using dpkg -i and it seems to >> >>>>>> install fine, with no warnings or errors. It boots and runs fine, >> >>>>>> even iSCSI. But, the odd issue is that the machine name in the >> >>>>>> prompt is wrong. As you can see from above, it went from: >> >>>>>> >> >>>>>> actual# >> >>>>>> >> >>>>>> To: >> >>>>>> >> >>>>>> vps5000# >> >>>>>> >> >>>>>> The name of the machine in /etc/hostname is actual and vps5000 is >> >>>>>> the highest number vps I have. Is this a serious issue or can I >> >>>>>> safely ignore it? >> >>>>>> >> >>>>>> Thanks... >> >>>>>> >> >>>>>> Jim >> >>>>>> >> > -- >> > --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering ---- >> > / ola@opalsys.net Annebergsslingan 37 \ >> >| opal@debian.org 654 65 KARLSTAD | >> >| http://opalsys.net/ Mobile: +46 (0)70-332 1551 | >> > \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / >> > --------------------------------------------------------------- >> >> >> >> >> > > -- > --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering ---- > / ola@opalsys.net Annebergsslingan 37 \ >| opal@debian.org 654 65 KARLSTAD | >| http://opalsys.net/ Mobile: +46 (0)70-332 1551 | > \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / > ---------------------------------------------------------------
Hi Jim You simply write a mail to submit@bugs.debian.org In the begiggning of the mail, before anything else, you write: Package: kernel-patch-openvz Severity: important And then you describe the fault. It is as simple as that. :) On Fri, Sep 14, 2007 at 05:25:43PM -0400, Jim Archer wrote: > Hi Ola... > > As embarrassing as this is, I have to admit that I can't figure out how to > open a bug report using the link provided below. That's why the report is See above. > not filed yet. Also, I experienced a kernel panic with this kernel. Not good. Please file a separate bug about that. I would like to know what you did when the kernel crashed, so I can debug the problem further. > Another engineer restarted the system, but because he was accessing via an > IPMI card (so no text console) he was unable to copy out the associated > information from the kernel. If there is something I can get you from the > machine, I'll be happy to do so. That would be good. > Also, another person I know knows how to open Debian bug reports, but he > won't be available until after the Jewish holiday. As soon as I can talk > with him I'll open the bug. With the above explanation I assume that you can write one on your own. :) In the meantime I have looked through the VZ patch and have not found anything obvious that explains your hostname problem. It seems like all the places where system_utsname has really been replaced with utsname() and the utsname() function is identical with the original vz patch. So it is likely something else. However the patch is huge so I may have made a couple of mistakes. Best regards, // Ola > > > > > --On Thursday, September 13, 2007 9:19 AM +0200 Ola Lundqvist > <ola@opalsys.net> wrote: > > >Hi > > > >kernel-patch-openvz > > > >Best regards, > > > >// Ola > > > >On Thu, Sep 13, 2007 at 02:12:19AM -0400, Jim Archer wrote: > >>Thanks very much Ola. What package do you want the bug reported against? > >> > >> > >>--On Thursday, September 13, 2007 7:07 AM +0200 Ola Lundqvist > >><ola@opalsys.net> wrote: > >> > >>> Hi Jim > >>> > >>> That depends on what you have on the system. In some cases the > >>> configuration is dependent on the hostname. For example exim can get a > >>> bit confused if the hostname is not the correct one. > >>> > >>> I will start to look on this bug asap. As Kir said something must have > >>> become wrong when the patchset was merged to Debian. > >>> > >>> Best regards, > >>> > >>> // Ola > >>> > >>> On Wed, Sep 12, 2007 at 04:59:33PM -0400, Jim Archer wrote: > >>>> Okay, I'll file the bug report tonight. Is there a reason I should > >>>> stop using this kernel, or is this a minor issue? > >>>> > >>>> --On Thursday, September 13, 2007 12:55 AM +0400 Kir Kolyshkin > >>>> <kir@openvz.org> wrote: > >>>> > >>>>> Thanks for reporting. Apparently when porting OpenVZ patchset to > >>>>> debian kernel utsname() virtualization got screwed... I suggest you > >>>>> to file a bug to http://bugs.debian.org/, and I have added Debian > >>>>> maintainer of OpenVZ packages to cc. > >>>>> > >>>>> Jim Archer wrote: > >>>>>> When logged into the main system: > >>>>>> > >>>>>> vps5000:~# hostname > >>>>>> vps5000.regtek.com > >>>>>> vps5000:~# vzlist > >>>>>> VEID NPROC STATUS IP_ADDR HOSTNAME > >>>>>> 102 13 running 72.46.65.30 nsp4.registrationtek.com > >>>>>> 104 21 running 72.46.65.47 > >>>>>> mail5.registrationtek.com 105 22 running 72.46.65.48 > >>>>>> whois.registrationtek.com 106 4 running 72.46.65.54 > >>>>>> gz.registrationtek.com 107 7 running 72.46.65.34 > >>>>>> squid.registrationtek.com 1000 4 running 72.46.67.2 > >>>>>> vps1000.regtek.com 1001 39 running 72.46.67.3 > >>>>>> vps1002.registrationtek.com 1002 29 running 72.46.67.7 > >>>>>> tocco.regtek.com 1003 23 running 72.46.67.8 > >>>>>> firstclass.regtek.com 5000 4 running 72.46.65.254 > >>>>>> vps5000.regtek.com > >>>>>> vps5000:~# vzctl enter 102 > >>>>>> entered into VE 102 > >>>>>> vps5000:/# hostname > >>>>>> vps5000.regtek.com > >>>>>> vps5000:/# exit > >>>>>> logout > >>>>>> exited from VE 102 > >>>>>> vps5000:~# vzctl enter 104 > >>>>>> entered into VE 104 > >>>>>> vps5000:/# hostname > >>>>>> vps5000.regtek.com > >>>>>> vps5000:/# exit > >>>>>> logout > >>>>>> exited from VE 104 > >>>>>> vps5000:~# vzctl enter 1003 > >>>>>> entered into VE 1003 > >>>>>> vps5000:/# hostname > >>>>>> vps5000.regtek.com > >>>>>> vps5000:/# exit > >>>>>> logout > >>>>>> exited from VE 1003 > >>>>>> vps5000:~# > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> --On Wednesday, September 12, 2007 1:30 PM +0400 Kir Kolyshkin > >>>>>> <kir@openvz.org> wrote: > >>>>>> > >>>>>>> Jim, > >>>>>>> > >>>>>>> Can you run hostname on the host system and inside a couple of VEs? > >>>>>>> Do they show the same or different hostnames? > >>>>>>> > >>>>>>> Jim Archer wrote: > >>>>>>>> Hi All... > >>>>>>>> > >>>>>>>> I just upgraded the kernel on my machine from: > >>>>>>>> > >>>>>>>> actual:/home/jim/openvz/kernels# uname -a > >>>>>>>> Linux actual.registrationtek.com 2.6.18-openvz-12-1etch1-amd64 #1 > >>>>>>>> SMP Fri May 4 23:37:24 MSD 2007 x86_64 GNU/Linux > >>>>>>>> > >>>>>>>> To: > >>>>>>>> > >>>>>>>> vps5000:~# uname -a > >>>>>>>> Linux vps5000.regtek.com 2.6.18-openvz-13-39.1d1-amd64 #1 SMP Mon > >>>>>>>> Sep 3 10:11:00 MSD 2007 x86_64 GNU/Linux > >>>>>>>> > >>>>>>>> > >>>>>>>> I did this because I have been having a memory consumption problem > >>>>>>>> with Exim4 I was hoping to resolve. I had been told that the > >>>>>>>> Exim4 memory issue was a known issue and was fixed in later > >>>>>>>> kernels. > >>>>>>>> > >>>>>>>> Anyhow, I installed the new kernel using dpkg -i and it seems to > >>>>>>>> install fine, with no warnings or errors. It boots and runs fine, > >>>>>>>> even iSCSI. But, the odd issue is that the machine name in the > >>>>>>>> prompt is wrong. As you can see from above, it went from: > >>>>>>>> > >>>>>>>> actual# > >>>>>>>> > >>>>>>>> To: > >>>>>>>> > >>>>>>>> vps5000# > >>>>>>>> > >>>>>>>> The name of the machine in /etc/hostname is actual and vps5000 is > >>>>>>>> the highest number vps I have. Is this a serious issue or can I > >>>>>>>> safely ignore it? > >>>>>>>> > >>>>>>>> Thanks... > >>>>>>>> > >>>>>>>> Jim > >>>>>>>> > >>> -- > >>> --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering ---- > >>> / ola@opalsys.net Annebergsslingan 37 \ > >>>| opal@debian.org 654 65 KARLSTAD | > >>>| http://opalsys.net/ Mobile: +46 (0)70-332 1551 | > >>> \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / > >>> --------------------------------------------------------------- > >> > >> > >> > >> > >> > > > >-- > > --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering ---- > >/ ola@opalsys.net Annebergsslingan 37 \ > >| opal@debian.org 654 65 KARLSTAD | > >| http://opalsys.net/ Mobile: +46 (0)70-332 1551 | > >\ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / > > --------------------------------------------------------------- > > > > > -- --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering ---- / ola@opalsys.net Annebergsslingan 37 \ | opal@debian.org 654 65 KARLSTAD | | http://opalsys.net/ Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / ---------------------------------------------------------------
Hi Problem found by Alexey Dobriyan <adobriyan@sw.ru>. I'm now building new source package and kernel packages. Best regards, // Ola On Thu, Sep 13, 2007 at 12:55:13AM +0400, Kir Kolyshkin wrote: > Thanks for reporting. Apparently when porting OpenVZ patchset to debian > kernel utsname() virtualization got screwed... I suggest you to file a > bug to http://bugs.debian.org/, and I have added Debian maintainer of > OpenVZ packages to cc. > > Jim Archer wrote: > > When logged into the main system: > > > > vps5000:~# hostname > > vps5000.regtek.com > > vps5000:~# vzlist > > VEID NPROC STATUS IP_ADDR HOSTNAME > > 102 13 running 72.46.65.30 nsp4.registrationtek.com > > 104 21 running 72.46.65.47 mail5.registrationtek.com > > 105 22 running 72.46.65.48 whois.registrationtek.com > > 106 4 running 72.46.65.54 gz.registrationtek.com > > 107 7 running 72.46.65.34 squid.registrationtek.com > > 1000 4 running 72.46.67.2 vps1000.regtek.com > > 1001 39 running 72.46.67.3 vps1002.registrationtek.com > > 1002 29 running 72.46.67.7 tocco.regtek.com > > 1003 23 running 72.46.67.8 firstclass.regtek.com > > 5000 4 running 72.46.65.254 vps5000.regtek.com > > vps5000:~# vzctl enter 102 > > entered into VE 102 > > vps5000:/# hostname > > vps5000.regtek.com > > vps5000:/# exit > > logout > > exited from VE 102 > > vps5000:~# vzctl enter 104 > > entered into VE 104 > > vps5000:/# hostname > > vps5000.regtek.com > > vps5000:/# exit > > logout > > exited from VE 104 > > vps5000:~# vzctl enter 1003 > > entered into VE 1003 > > vps5000:/# hostname > > vps5000.regtek.com > > vps5000:/# exit > > logout > > exited from VE 1003 > > vps5000:~# > > > > > > > > > > --On Wednesday, September 12, 2007 1:30 PM +0400 Kir Kolyshkin > > <kir@openvz.org> wrote: > > > >> Jim, > >> > >> Can you run hostname on the host system and inside a couple of VEs? Do > >> they show the same or different hostnames? > >> > >> Jim Archer wrote: > >>> Hi All... > >>> > >>> I just upgraded the kernel on my machine from: > >>> > >>> actual:/home/jim/openvz/kernels# uname -a > >>> Linux actual.registrationtek.com 2.6.18-openvz-12-1etch1-amd64 #1 SMP > >>> Fri May 4 23:37:24 MSD 2007 x86_64 GNU/Linux > >>> > >>> To: > >>> > >>> vps5000:~# uname -a > >>> Linux vps5000.regtek.com 2.6.18-openvz-13-39.1d1-amd64 #1 SMP Mon Sep > >>> 3 10:11:00 MSD 2007 x86_64 GNU/Linux > >>> > >>> > >>> I did this because I have been having a memory consumption problem > >>> with Exim4 I was hoping to resolve. I had been told that the Exim4 > >>> memory issue was a known issue and was fixed in later kernels. > >>> > >>> Anyhow, I installed the new kernel using dpkg -i and it seems to > >>> install fine, with no warnings or errors. It boots and runs fine, > >>> even iSCSI. But, the odd issue is that the machine name in the prompt > >>> is wrong. As you can see from above, it went from: > >>> > >>> actual# > >>> > >>> To: > >>> > >>> vps5000# > >>> > >>> The name of the machine in /etc/hostname is actual and vps5000 is the > >>> highest number vps I have. Is this a serious issue or can I safely > >>> ignore it? > >>> > >>> Thanks... > >>> > >>> Jim > >>> -- --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering ---- / ola@opalsys.net Annebergsslingan 37 \ | opal@debian.org 654 65 KARLSTAD | | http://opalsys.net/ Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / ---------------------------------------------------------------
Hi Ola and thanks very much! I'm wondering, could this problem have caused a kernel panic? --On Friday, September 28, 2007 10:14 PM +0200 Ola Lundqvist <ola@opalsys.net> wrote: > Hi > > Problem found by Alexey Dobriyan <adobriyan@sw.ru>. I'm now building new > source package and kernel packages. > > Best regards, > > // Ola > > On Thu, Sep 13, 2007 at 12:55:13AM +0400, Kir Kolyshkin wrote: >> Thanks for reporting. Apparently when porting OpenVZ patchset to debian >> kernel utsname() virtualization got screwed... I suggest you to file a >> bug to http://bugs.debian.org/, and I have added Debian maintainer of >> OpenVZ packages to cc. >> >> Jim Archer wrote: >> > When logged into the main system: >> > >> > vps5000:~# hostname >> > vps5000.regtek.com >> > vps5000:~# vzlist >> > VEID NPROC STATUS IP_ADDR HOSTNAME >> > 102 13 running 72.46.65.30 nsp4.registrationtek.com >> > 104 21 running 72.46.65.47 mail5.registrationtek.com >> > 105 22 running 72.46.65.48 whois.registrationtek.com >> > 106 4 running 72.46.65.54 gz.registrationtek.com >> > 107 7 running 72.46.65.34 squid.registrationtek.com >> > 1000 4 running 72.46.67.2 vps1000.regtek.com >> > 1001 39 running 72.46.67.3 >> > vps1002.registrationtek.com 1002 29 running 72.46.67.7 >> > tocco.regtek.com 1003 23 running 72.46.67.8 >> > firstclass.regtek.com 5000 4 running 72.46.65.254 >> > vps5000.regtek.com >> > vps5000:~# vzctl enter 102 >> > entered into VE 102 >> > vps5000:/# hostname >> > vps5000.regtek.com >> > vps5000:/# exit >> > logout >> > exited from VE 102 >> > vps5000:~# vzctl enter 104 >> > entered into VE 104 >> > vps5000:/# hostname >> > vps5000.regtek.com >> > vps5000:/# exit >> > logout >> > exited from VE 104 >> > vps5000:~# vzctl enter 1003 >> > entered into VE 1003 >> > vps5000:/# hostname >> > vps5000.regtek.com >> > vps5000:/# exit >> > logout >> > exited from VE 1003 >> > vps5000:~# >> > >> > >> > >> > >> > --On Wednesday, September 12, 2007 1:30 PM +0400 Kir Kolyshkin >> > <kir@openvz.org> wrote: >> > >> >> Jim, >> >> >> >> Can you run hostname on the host system and inside a couple of VEs? Do >> >> they show the same or different hostnames? >> >> >> >> Jim Archer wrote: >> >>> Hi All... >> >>> >> >>> I just upgraded the kernel on my machine from: >> >>> >> >>> actual:/home/jim/openvz/kernels# uname -a >> >>> Linux actual.registrationtek.com 2.6.18-openvz-12-1etch1-amd64 #1 SMP >> >>> Fri May 4 23:37:24 MSD 2007 x86_64 GNU/Linux >> >>> >> >>> To: >> >>> >> >>> vps5000:~# uname -a >> >>> Linux vps5000.regtek.com 2.6.18-openvz-13-39.1d1-amd64 #1 SMP Mon Sep >> >>> 3 10:11:00 MSD 2007 x86_64 GNU/Linux >> >>> >> >>> >> >>> I did this because I have been having a memory consumption problem >> >>> with Exim4 I was hoping to resolve. I had been told that the Exim4 >> >>> memory issue was a known issue and was fixed in later kernels. >> >>> >> >>> Anyhow, I installed the new kernel using dpkg -i and it seems to >> >>> install fine, with no warnings or errors. It boots and runs fine, >> >>> even iSCSI. But, the odd issue is that the machine name in the prompt >> >>> is wrong. As you can see from above, it went from: >> >>> >> >>> actual# >> >>> >> >>> To: >> >>> >> >>> vps5000# >> >>> >> >>> The name of the machine in /etc/hostname is actual and vps5000 is the >> >>> highest number vps I have. Is this a serious issue or can I safely >> >>> ignore it? >> >>> >> >>> Thanks... >> >>> >> >>> Jim >> >>> > -- > --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering ---- > / ola@opalsys.net Annebergsslingan 37 \ >| opal@debian.org 654 65 KARLSTAD | >| http://opalsys.net/ Mobile: +46 (0)70-332 1551 | > \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / > ---------------------------------------------------------------
Hi On Fri, Sep 28, 2007 at 04:25:39PM -0400, Jim Archer wrote: > Hi Ola and thanks very much! > > I'm wondering, could this problem have caused a kernel panic? Not likely, but you never know. Best regards, // Ola > > > --On Friday, September 28, 2007 10:14 PM +0200 Ola Lundqvist > <ola@opalsys.net> wrote: > > >Hi > > > >Problem found by Alexey Dobriyan <adobriyan@sw.ru>. I'm now building new > >source package and kernel packages. > > > >Best regards, > > > >// Ola > > > >On Thu, Sep 13, 2007 at 12:55:13AM +0400, Kir Kolyshkin wrote: > >>Thanks for reporting. Apparently when porting OpenVZ patchset to debian > >>kernel utsname() virtualization got screwed... I suggest you to file a > >>bug to http://bugs.debian.org/, and I have added Debian maintainer of > >>OpenVZ packages to cc. > >> > >>Jim Archer wrote: > >>> When logged into the main system: > >>> > >>> vps5000:~# hostname > >>> vps5000.regtek.com > >>> vps5000:~# vzlist > >>> VEID NPROC STATUS IP_ADDR HOSTNAME > >>> 102 13 running 72.46.65.30 nsp4.registrationtek.com > >>> 104 21 running 72.46.65.47 mail5.registrationtek.com > >>> 105 22 running 72.46.65.48 whois.registrationtek.com > >>> 106 4 running 72.46.65.54 gz.registrationtek.com > >>> 107 7 running 72.46.65.34 squid.registrationtek.com > >>> 1000 4 running 72.46.67.2 vps1000.regtek.com > >>> 1001 39 running 72.46.67.3 > >>> vps1002.registrationtek.com 1002 29 running 72.46.67.7 > >>> tocco.regtek.com 1003 23 running 72.46.67.8 > >>> firstclass.regtek.com 5000 4 running 72.46.65.254 > >>> vps5000.regtek.com > >>> vps5000:~# vzctl enter 102 > >>> entered into VE 102 > >>> vps5000:/# hostname > >>> vps5000.regtek.com > >>> vps5000:/# exit > >>> logout > >>> exited from VE 102 > >>> vps5000:~# vzctl enter 104 > >>> entered into VE 104 > >>> vps5000:/# hostname > >>> vps5000.regtek.com > >>> vps5000:/# exit > >>> logout > >>> exited from VE 104 > >>> vps5000:~# vzctl enter 1003 > >>> entered into VE 1003 > >>> vps5000:/# hostname > >>> vps5000.regtek.com > >>> vps5000:/# exit > >>> logout > >>> exited from VE 1003 > >>> vps5000:~# > >>> > >>> > >>> > >>> > >>> --On Wednesday, September 12, 2007 1:30 PM +0400 Kir Kolyshkin > >>> <kir@openvz.org> wrote: > >>> > >>>> Jim, > >>>> > >>>> Can you run hostname on the host system and inside a couple of VEs? Do > >>>> they show the same or different hostnames? > >>>> > >>>> Jim Archer wrote: > >>>>> Hi All... > >>>>> > >>>>> I just upgraded the kernel on my machine from: > >>>>> > >>>>> actual:/home/jim/openvz/kernels# uname -a > >>>>> Linux actual.registrationtek.com 2.6.18-openvz-12-1etch1-amd64 #1 SMP > >>>>> Fri May 4 23:37:24 MSD 2007 x86_64 GNU/Linux > >>>>> > >>>>> To: > >>>>> > >>>>> vps5000:~# uname -a > >>>>> Linux vps5000.regtek.com 2.6.18-openvz-13-39.1d1-amd64 #1 SMP Mon Sep > >>>>> 3 10:11:00 MSD 2007 x86_64 GNU/Linux > >>>>> > >>>>> > >>>>> I did this because I have been having a memory consumption problem > >>>>> with Exim4 I was hoping to resolve. I had been told that the Exim4 > >>>>> memory issue was a known issue and was fixed in later kernels. > >>>>> > >>>>> Anyhow, I installed the new kernel using dpkg -i and it seems to > >>>>> install fine, with no warnings or errors. It boots and runs fine, > >>>>> even iSCSI. But, the odd issue is that the machine name in the prompt > >>>>> is wrong. As you can see from above, it went from: > >>>>> > >>>>> actual# > >>>>> > >>>>> To: > >>>>> > >>>>> vps5000# > >>>>> > >>>>> The name of the machine in /etc/hostname is actual and vps5000 is the > >>>>> highest number vps I have. Is this a serious issue or can I safely > >>>>> ignore it? > >>>>> > >>>>> Thanks... > >>>>> > >>>>> Jim > >>>>> > >-- > > --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering ---- > >/ ola@opalsys.net Annebergsslingan 37 \ > >| opal@debian.org 654 65 KARLSTAD | > >| http://opalsys.net/ Mobile: +46 (0)70-332 1551 | > >\ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / > > --------------------------------------------------------------- > > > > > -- --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering ---- / ola@opalsys.net Annebergsslingan 37 \ | opal@debian.org 654 65 KARLSTAD | | http://opalsys.net/ Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / ---------------------------------------------------------------
Jim, oops dump from dmesg or /var/log/messages or even picture of screen would be helpful to identify the problem. Thanks, Kirill Jim Archer wrote: > Hi Ola and thanks very much! > > I'm wondering, could this problem have caused a kernel panic? > > > > --On Friday, September 28, 2007 10:14 PM +0200 Ola Lundqvist > <ola@opalsys.net> wrote: > > >>Hi >> >>Problem found by Alexey Dobriyan <adobriyan@sw.ru>. I'm now building new >>source package and kernel packages. >> >>Best regards, >> >>// Ola >> >>On Thu, Sep 13, 2007 at 12:55:13AM +0400, Kir Kolyshkin wrote: >> >>>Thanks for reporting. Apparently when porting OpenVZ patchset to debian >>>kernel utsname() virtualization got screwed... I suggest you to file a >>>bug to http://bugs.debian.org/, and I have added Debian maintainer of >>>OpenVZ packages to cc. >>> >>>Jim Archer wrote: >>> >>>>When logged into the main system: >>>> >>>>vps5000:~# hostname >>>>vps5000.regtek.com >>>>vps5000:~# vzlist >>>> VEID NPROC STATUS IP_ADDR HOSTNAME >>>> 102 13 running 72.46.65.30 nsp4.registrationtek.com >>>> 104 21 running 72.46.65.47 mail5.registrationtek.com >>>> 105 22 running 72.46.65.48 whois.registrationtek.com >>>> 106 4 running 72.46.65.54 gz.registrationtek.com >>>> 107 7 running 72.46.65.34 squid.registrationtek.com >>>> 1000 4 running 72.46.67.2 vps1000.regtek.com >>>> 1001 39 running 72.46.67.3 >>>> vps1002.registrationtek.com 1002 29 running 72.46.67.7 >>>> tocco.regtek.com 1003 23 running 72.46.67.8 >>>> firstclass.regtek.com 5000 4 running 72.46.65.254 >>>> vps5000.regtek.com >>>>vps5000:~# vzctl enter 102 >>>>entered into VE 102 >>>>vps5000:/# hostname >>>>vps5000.regtek.com >>>>vps5000:/# exit >>>>logout >>>>exited from VE 102 >>>>vps5000:~# vzctl enter 104 >>>>entered into VE 104 >>>>vps5000:/# hostname >>>>vps5000.regtek.com >>>>vps5000:/# exit >>>>logout >>>>exited from VE 104 >>>>vps5000:~# vzctl enter 1003 >>>>entered into VE 1003 >>>>vps5000:/# hostname >>>>vps5000.regtek.com >>>>vps5000:/# exit >>>>logout >>>>exited from VE 1003 >>>>vps5000:~# >>>> >>>> >>>> >>>> >>>>--On Wednesday, September 12, 2007 1:30 PM +0400 Kir Kolyshkin >>>><kir@openvz.org> wrote: >>>> >>>> >>>>>Jim, >>>>> >>>>>Can you run hostname on the host system and inside a couple of VEs? Do >>>>>they show the same or different hostnames? >>>>> >>>>>Jim Archer wrote: >>>>> >>>>>>Hi All... >>>>>> >>>>>>I just upgraded the kernel on my machine from: >>>>>> >>>>>>actual:/home/jim/openvz/kernels# uname -a >>>>>>Linux actual.registrationtek.com 2.6.18-openvz-12-1etch1-amd64 #1 SMP >>>>>>Fri May 4 23:37:24 MSD 2007 x86_64 GNU/Linux >>>>>> >>>>>>To: >>>>>> >>>>>>vps5000:~# uname -a >>>>>>Linux vps5000.regtek.com 2.6.18-openvz-13-39.1d1-amd64 #1 SMP Mon Sep >>>>>>3 10:11:00 MSD 2007 x86_64 GNU/Linux >>>>>> >>>>>> >>>>>>I did this because I have been having a memory consumption problem >>>>>>with Exim4 I was hoping to resolve. I had been told that the Exim4 >>>>>>memory issue was a known issue and was fixed in later kernels. >>>>>> >>>>>>Anyhow, I installed the new kernel using dpkg -i and it seems to >>>>>>install fine, with no warnings or errors. It boots and runs fine, >>>>>>even iSCSI. But, the odd issue is that the machine name in the prompt >>>>>>is wrong. As you can see from above, it went from: >>>>>> >>>>>>actual# >>>>>> >>>>>>To: >>>>>> >>>>>>vps5000# >>>>>> >>>>>>The name of the machine in /etc/hostname is actual and vps5000 is the >>>>>>highest number vps I have. Is this a serious issue or can I safely >>>>>>ignore it? >>>>>> >>>>>>Thanks... >>>>>> >>>>>>Jim >>>>>> >>-- >> --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering ---- >>/ ola@opalsys.net Annebergsslingan 37 \ >>| opal@debian.org 654 65 KARLSTAD | >>| http://opalsys.net/ Mobile: +46 (0)70-332 1551 | >>\ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / >> --------------------------------------------------------------- > > > > > >