[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Testbed-admins] Can't get interactive mode while trying to test images

To: testbed-admins@flux.utah.edu
From: Ben Burnett <bburnett@atcorp.com>
Subject: Re: [Testbed-admins] Can't get interactive mode while trying to test images
Date: Tue, 14 Jul 2009 11:40:31 -0500

here is the tftp.log for this morning (3 or 4 reboots of pc1 and pc2):

Jul 14 10:22:09 boss tftpd[93168]: 192.168.1.1/2070: RRQ for
/tftpboot/pxeboot.emu (remapped to /pxeboot.emu)
Jul 14 10:22:09 boss tftpd[93168]: tftp: client does not accept options
Jul 14 10:22:09 boss tftpd[93168]: 192.168.1.1/2070: RRQ done
Jul 14 10:22:09 boss tftpd[1294]: pid 93168 exits, numchildren=0
Jul 14 10:22:09 boss tftpd[93169]: 192.168.1.1/2071: RRQ for
/tftpboot/pxeboot.emu (remapped to /pxeboot.emu)
Jul 14 10:22:10 boss tftpd[93169]: 192.168.1.1/2071: RRQ done
Jul 14 10:22:10 boss tftpd[1294]: pid 93169 exits, numchildren=0
Jul 14 10:22:10 boss tftpd[93170]: 192.168.1.1/2548: RRQ for
/tftpboot/freebsd/boot/loader.rc.gz (remapped to
/freebsd/boot/loader.rc.gz)
Jul 14 10:22:10 boss tftpd[93170]: 192.168.1.1/2548: RRQ done
Jul 14 10:22:10 boss tftpd[1294]: pid 93170 exits, numchildren=0
Jul 14 10:22:10 boss tftpd[93171]: 192.168.1.1/2549: RRQ for
/tftpboot/freebsd/boot/loader.conf.gz (remapped to
/freebsd/boot/loader.conf.gz)
Jul 14 10:22:10 boss tftpd[93171]: 192.168.1.1/2549: RRQ done
Jul 14 10:22:10 boss tftpd[1294]: pid 93171 exits, numchildren=0
Jul 14 10:22:10 boss tftpd[93172]: 192.168.1.1/2550: RRQ for
/tftpboot/freebsd/boot/kernel.gz (remapped to /freebsd/boot/kernel.gz)
Jul 14 10:22:15 boss tftpd[93172]: 192.168.1.1/2550: RRQ done
Jul 14 10:22:15 boss tftpd[1294]: pid 93172 exits, numchildren=0
Jul 14 10:22:15 boss tftpd[93173]: 192.168.1.1/2553: RRQ for
/tftpboot/freebsd/boot/mfsroot.gz (remapped to
/freebsd/boot/mfsroot.gz)
Jul 14 10:22:29 boss tftpd[93173]: 192.168.1.1/2553: RRQ done
Jul 14 10:22:29 boss tftpd[1294]: pid 93173 exits, numchildren=0
Jul 14 10:22:29 boss tftpd[93175]: 192.168.1.1/2567: RRQ for
/tftpboot/freebsd/boot/acpi.ko.gz (remapped to
/freebsd/boot/acpi.ko.gz)
Jul 14 10:22:29 boss tftpd[93175]: 192.168.1.1/2567: RRQ done
Jul 14 10:22:29 boss tftpd[1294]: pid 93175 exits, numchildren=0
Jul 14 10:24:25 boss tftpd[93204]: 192.168.1.2/2070: RRQ for
/tftpboot/pxeboot.emu (remapped to /pxeboot.emu)
Jul 14 10:24:25 boss tftpd[93204]: tftp: client does not accept options
Jul 14 10:24:25 boss tftpd[93204]: 192.168.1.2/2070: RRQ done
Jul 14 10:24:25 boss tftpd[1294]: pid 93204 exits, numchildren=0
Jul 14 10:24:25 boss tftpd[93205]: 192.168.1.2/2071: RRQ for
/tftpboot/pxeboot.emu (remapped to /pxeboot.emu)
Jul 14 10:24:26 boss tftpd[93205]: 192.168.1.2/2071: RRQ done
Jul 14 10:24:26 boss tftpd[1294]: pid 93205 exits, numchildren=0
Jul 14 10:24:26 boss tftpd[93206]: 192.168.1.2/2798: RRQ for
/tftpboot/freebsd/boot/loader.rc.gz (remapped to
/freebsd/boot/loader.rc.gz)
Jul 14 10:24:26 boss tftpd[93206]: 192.168.1.2/2798: RRQ done
Jul 14 10:24:26 boss tftpd[1294]: pid 93206 exits, numchildren=0
Jul 14 10:24:26 boss tftpd[93207]: 192.168.1.2/2799: RRQ for
/tftpboot/freebsd/boot/loader.conf.gz (remapped to
/freebsd/boot/loader.conf.gz)
Jul 14 10:24:26 boss tftpd[93207]: 192.168.1.2/2799: RRQ done
Jul 14 10:24:26 boss tftpd[1294]: pid 93207 exits, numchildren=0
Jul 14 10:24:26 boss tftpd[93208]: 192.168.1.2/2800: RRQ for
/tftpboot/freebsd/boot/kernel.gz (remapped to /freebsd/boot/kernel.gz)
Jul 14 10:24:31 boss tftpd[93208]: 192.168.1.2/2800: RRQ done
Jul 14 10:24:31 boss tftpd[1294]: pid 93208 exits, numchildren=0
Jul 14 10:24:31 boss tftpd[93209]: 192.168.1.2/2803: RRQ for
/tftpboot/freebsd/boot/mfsroot.gz (remapped to
/freebsd/boot/mfsroot.gz)
Jul 14 10:24:45 boss tftpd[93209]: 192.168.1.2/2803: RRQ done
Jul 14 10:24:45 boss tftpd[1294]: pid 93209 exits, numchildren=0
Jul 14 10:24:45 boss tftpd[93219]: 192.168.1.2/2817: RRQ for
/tftpboot/freebsd/boot/acpi.ko.gz (remapped to
/freebsd/boot/acpi.ko.gz)
Jul 14 10:24:45 boss tftpd[93219]: 192.168.1.2/2817: RRQ done
Jul 14 10:24:45 boss tftpd[1294]: pid 93219 exits, numchildren=0
Jul 14 10:34:48 boss tftpd[93328]: 192.168.1.2/2070: RRQ for
/tftpboot/pxeboot.emu (remapped to /pxeboot.emu)
Jul 14 10:34:48 boss tftpd[93328]: tftp: client does not accept options
Jul 14 10:34:48 boss tftpd[93328]: 192.168.1.2/2070: RRQ done
Jul 14 10:34:48 boss tftpd[1294]: pid 93328 exits, numchildren=0
Jul 14 10:34:48 boss tftpd[93329]: 192.168.1.2/2071: RRQ for
/tftpboot/pxeboot.emu (remapped to /pxeboot.emu)
Jul 14 10:34:48 boss tftpd[93329]: 192.168.1.2/2071: RRQ done
Jul 14 10:34:48 boss tftpd[1294]: pid 93329 exits, numchildren=0
Jul 14 10:34:48 boss tftpd[93330]: 192.168.1.2/2396: RRQ for
/tftpboot/freebsd/boot/loader.rc.gz (remapped to
/freebsd/boot/loader.rc.gz)
Jul 14 10:34:48 boss tftpd[93330]: 192.168.1.2/2396: RRQ done
Jul 14 10:34:48 boss tftpd[1294]: pid 93330 exits, numchildren=0
Jul 14 10:34:48 boss tftpd[93331]: 192.168.1.2/2397: RRQ for
/tftpboot/freebsd/boot/loader.conf.gz (remapped to
/freebsd/boot/loader.conf.gz)
Jul 14 10:34:48 boss tftpd[93331]: 192.168.1.2/2397: RRQ done
Jul 14 10:34:48 boss tftpd[1294]: pid 93331 exits, numchildren=0
Jul 14 10:34:48 boss tftpd[93332]: 192.168.1.2/2398: RRQ for
/tftpboot/freebsd/boot/kernel.gz (remapped to /freebsd/boot/kernel.gz)
Jul 14 10:34:53 boss tftpd[93332]: 192.168.1.2/2398: RRQ done
Jul 14 10:34:53 boss tftpd[1294]: pid 93332 exits, numchildren=0
Jul 14 10:34:53 boss tftpd[93334]: 192.168.1.2/2401: RRQ for
/tftpboot/freebsd/boot/mfsroot.gz (remapped to
/freebsd/boot/mfsroot.gz)
Jul 14 10:35:06 boss tftpd[93334]: 192.168.1.2/2401: RRQ done
Jul 14 10:35:06 boss tftpd[1294]: pid 93334 exits, numchildren=0
Jul 14 10:35:06 boss tftpd[93344]: 192.168.1.2/2415: RRQ for
/tftpboot/freebsd/boot/acpi.ko.gz (remapped to
/freebsd/boot/acpi.ko.gz)
Jul 14 10:35:07 boss tftpd[93344]: 192.168.1.2/2415: RRQ done
Jul 14 10:35:07 boss tftpd[1294]: pid 93344 exits, numchildren=0



Ben Burnett
  R&D Software Engineer: wired, wireless, ad hoc, mesh networking,
    network monitoring and data visualization
  ATC (Architecture Technology Corporation)   http://www.atcorp.com/
  bburnett@atcorp.com                         (952) 829-5864 x167
  --------Views expressed are mine and not those of ATC--------
  Personal:
    ben@burnett.ws                            http://www.burnett.ws/
http://ben.burnett.ws/
http://www.linkedin.com/in/benburnett



On Tue, Jul 14, 2009 at 11:37 AM, Ben Burnett<bburnett@atcorp.com> wrote:
> we never see the prompt at all, it boots directly to the admin mfs
> image....   so it appears to be talking fine to the pxe boot loader on
> boss.... ( I think)
>
>
> Ben Burnett
>  R&D Software Engineer: wired, wireless, ad hoc, mesh networking,
>    network monitoring and data visualization
>  ATC (Architecture Technology Corporation)   http://www.atcorp.com/
>  bburnett@atcorp.com                         (952) 829-5864 x167
>  --------Views expressed are mine and not those of ATC--------
>  Personal:
>    ben@burnett.ws                            http://www.burnett.ws/
> http://ben.burnett.ws/
> http://www.linkedin.com/in/benburnett
>
>
>
> On Tue, Jul 14, 2009 at 11:29 AM, Mike Hibler<mike@flux.utah.edu> wrote:
>> Are you seeing the prompt, but it isn't accepting your input?  Or are you
>> getting no prompt?  Are you seeing any output at all on the console?
>>
>> The loss of DB connection should not be related.
>>
>> On Tue, Jul 14, 2009 at 11:14:14AM -0500, Ben Burnett wrote:
>>> Leigh,
>>>
>>> The bootinfo.log entries for yesterday and today are:
>>> Jul 13 16:28:59 boss bootinfo[1239]: 192.168.1.1: REQUEST (vers 1)
>>> Jul 13 16:28:59 boss bootinfo[1239]: tbdb: query failed: MySQL server
>>> has gone away
>>> Jul 13 16:28:59 boss bootinfo[1239]: Lost connection to DB; Attempting
>>> to reconnect ...
>>> Jul 13 16:28:59 boss bootinfo[1239]: 192.168.1.1: REPLY: boot from mfs
>>> /tftpboot/freebsd
>>> Jul 13 16:44:26 boss bootinfo[1239]: 192.168.1.1: REQUEST (vers 1)
>>> Jul 13 16:44:26 boss bootinfo[1239]: 192.168.1.1: REPLY: boot from mfs
>>> /tftpboot/freebsd
>>> Jul 13 16:54:10 boss bootinfo[1239]: 192.168.1.1: REQUEST (vers 1)
>>> Jul 13 16:54:10 boss bootinfo[1239]: 192.168.1.1: REPLY: boot from mfs
>>> /tftpboot/freebsd
>>> Jul 14 08:51:25 boss bootinfo[1239]: 192.168.1.1: REQUEST (vers 1)
>>> Jul 14 08:51:25 boss bootinfo[1239]: tbdb: query failed: MySQL server
>>> has gone away
>>> Jul 14 08:51:25 boss bootinfo[1239]: Lost connection to DB; Attempting
>>> to reconnect ...
>>> Jul 14 08:51:25 boss bootinfo[1239]: 192.168.1.1: REPLY: boot from mfs
>>> /tftpboot/freebsd
>>> Jul 14 09:04:55 boss bootinfo[1239]: 192.168.1.1: REQUEST (vers 1)
>>> Jul 14 09:04:55 boss bootinfo[1239]: 192.168.1.1: REPLY: boot from mfs
>>> /tftpboot/freebsd
>>> Jul 14 09:13:11 boss bootinfo[1239]: 192.168.1.1: REQUEST (vers 1)
>>> Jul 14 09:13:11 boss bootinfo[1239]: 192.168.1.1: REPLY: boot from mfs
>>> /tftpboot/freebsd
>>> Jul 14 10:22:10 boss bootinfo[1239]: 192.168.1.1: REQUEST (vers 1)
>>> Jul 14 10:22:10 boss bootinfo[1239]: 192.168.1.1: REPLY: boot from mfs
>>> /tftpboot/freebsd
>>> Jul 14 10:24:26 boss bootinfo[1239]: 192.168.1.2: REQUEST (vers 1)
>>> Jul 14 10:24:26 boss bootinfo[1239]: 192.168.1.2: REPLY: boot from mfs
>>> /tftpboot/freebsd
>>> Jul 14 10:34:48 boss bootinfo[1239]: 192.168.1.2: REQUEST (vers 1)
>>> Jul 14 10:34:48 boss bootinfo[1239]: 192.168.1.2: REPLY: boot from mfs
>>> /tftpboot/freebsd
>>>
>>> any idea why it loses connection to the database?   would that cause problems?
>>>
>>>
>>> Ben Burnett
>>>   R&D Software Engineer: wired, wireless, ad hoc, mesh networking,
>>>     network monitoring and data visualization
>>>   ATC (Architecture Technology Corporation)   http://www.atcorp.com/
>>>   bburnett@atcorp.com                         (952) 829-5864 x167
>>>   --------Views expressed are mine and not those of ATC--------
>>>   Personal:
>>>     ben@burnett.ws                            http://www.burnett.ws/
>>> http://ben.burnett.ws/
>>> http://www.linkedin.com/in/benburnett
>>>
>>>
>>>
>>> On Tue, Jul 14, 2009 at 11:02 AM, Leigh Stoller<stoller@flux.utah.edu> wrote:
>>> >> Leigh,
>>> >> ? ?I'm having this same problem again where my nodes don't give me
>>> >> the option to go into interactive mode. ?I have 2 pc's with test
>>> >> images (pc1 and pc2) ?pc1 was in hwdown and pc2 was in reloading
>>> >> neither gave me the interactive mode option. ?I moved them both to
>>> >> hwdown per your commands from June and they show in hwdown but still
>>> >> no interactive mode option. ? What Am I missing?
>>> >
>>> > Hi Ben. What is /usr/testbed/log/bootinfo.log saying?
>>> >
>>> > Lbs
>>> >
>>> >
>>> >
>>>
>>> _______________________________________________
>>> Testbed-admins mailing list
>>> Testbed-admins@flux.utah.edu
>>> http://www.flux.utah.edu/mailman/listinfo/testbed-admins
>>
>>
>

References:
- [Testbed-admins] Can't get interactive mode while trying to test images
  - From: Ben Burnett <bburnett@atcorp.com>
- Re: [Testbed-admins] Can't get interactive mode while trying to test images
  - From: Leigh Stoller <stoller@flux.utah.edu>
- Re: [Testbed-admins] Can't get interactive mode while trying to test images
  - From: Ben Burnett <bburnett@atcorp.com>
- Re: [Testbed-admins] Can't get interactive mode while trying to test images
  - From: Mike Hibler <mike@flux.utah.edu>
- Re: [Testbed-admins] Can't get interactive mode while trying to test images
  - From: Ben Burnett <bburnett@atcorp.com>

Prev by Date: Re: [Testbed-admins] Can't get interactive mode while trying to test images
Next by Date: Re: [Testbed-admins] Can't get interactive mode while trying to test images
Previous by thread: Re: [Testbed-admins] Can't get interactive mode while trying to test images
Next by thread: Re: [Testbed-admins] Can't get interactive mode while trying to test images
Index(es):
- Date
- Thread