/bin/ipwatchd: error during PXE boot

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 3
Comments: 5

I am using the latest build of Snap Deploy (3470) and I am getting an error when booting the Snap Deploy Agent from PXE.

The scenario is this...

Machine powers up, goes to PXE boot, gets valid IP address, shows Acronis Boot menu, I choose Snap Deploy Agent, then after a few seconds I get the error shown in the attached screen shot.

Essentially, the error is:

/bin/ipwatchd: /lib/tis/libc.so.6: version 'BLIBC_2.4' not found (required by /bin/ipwatchd)

I have reconfigured the PXE boot media, but it doesn't help.

This error eventually times out, and continues to boot to the Snap Deploy Agent. I noticed the IP address was changed to 169.x.x.x. If I manually enter a valid ip address, DNS, deploy server address etc, then I can continue to deploy images to the machine.

Any recommendations?

PS: I am experiencing this on 2 identical Dell Optiplex 745 machines.

Thanks

Attachment Size
img_0729.jpg 473.49 KB
Fri, 02/18/2011 - 15:10
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 0
Comments: 1

We have the exact same error message.

You are using the PXE server. You have successfully created master images using the master image Creator via PXE. Our issue is deploying images and the application freezing after selecting deploy images..

Our DHCP server lease timeout is set to 7 days, no issue with IP address allocation and assigning. We are using the latest build of Snap Deploy 3470.

I have contacted their support asking a few questions but everything they have advised we have already done and tested. I will need to do some further testing and problem solving but let me know if you work out this issue.

In addition we are using HP 6730b Laptops and HP 8000 Elite/DC7800/DC7900 Desktops.

Thanks.

Mon, 02/21/2011 - 01:04
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 88
Comments: 4769

Hello Michael and Andrew,

Thank you for posting. I will do my best to help you.

The error message that you refer to is a generic message that can be safely ignored, I am sorry it has caused you this inconvenience.

Andrew, the issue that you are experiencing has nothing to do with this error message. I was able to find your open support case in our system and I am confident that the support professional working on your case will get it resolved.

If you need additional help, please let me know.

Thank you.

Thu, 02/24/2011 - 08:44
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 3
Comments: 5

Anton,

What do you mean this error can be safely ignored!? It is a huge problem for me. I cannot deploy an image without visiting the machine myself and inputting all the IP information manually. Not helpful when the machine isn't even at the same site as me.

There is something wrong with the PXE element of snap deploy and it needs a solution. It was working previously but not this time on this machine.

Please investigate this again.

Michael.

Thu, 02/24/2011 - 09:55
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 0
Comments: 2

Hi,
I have the same error in the same scenario and image is for 50 DELL Optiplex 380! I am using the latest build of Snap Deploy (3470) and I am getting an error when booting the Snap Deploy Agent from PXE (BLIBC_2.... too fast to read before the reboot). The server is a MS Windows 2003 R2 Std SP2.
What can we do?
Thanks.

Wed, 04/20/2011 - 11:42
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 3
Comments: 5

Hi,

This problem turned out to be a switch issue at our end. Something to do with STP being either enabled or disabled on the switches. Sorry this probably isn't the answer you wanted to hear.

Michael

Thu, 04/21/2011 - 09:08