HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- receiving bootp/ioctl errors in syslog... what to ...
Operating System - HP-UX
1834824
Members
2656
Online
110070
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2003 03:18 AM
03-19-2003 03:18 AM
receiving bootp/ioctl errors in syslog... what to do?
hi,
we have had a major network upgrade last weekend to gigabit switches and I have asked my network team to set the ports on the unix servers to 100FD. Since then on 1 server there are entries logged into the syslog for the last 3 days since that say the following.
-----------------------
Mar 18 02:22:46 jupiter bootpd[25831]: ioctl: Invalid argument
Mar 18 02:22:54 jupiter bootpd[25838]: bootpd 2.4 #1.17.213.3: Thu Oct 23 19:47:23 GMT 1997
Mar 18 02:22:54 jupiter bootpd[25838]: ioctl: Invalid argument
Mar 18 02:22:54 jupiter inetd[1489]: bootps/udp: Exit status 1
Mar 18 02:22:55 jupiter above message repeats 25 times
Mar 18 02:22:54 jupiter syslog: received short packet from 101.95.0.1
-----------------------
I will attach the full syslog!
any suggestions as to what is going on would be appreciated!
we have had a major network upgrade last weekend to gigabit switches and I have asked my network team to set the ports on the unix servers to 100FD. Since then on 1 server there are entries logged into the syslog for the last 3 days since that say the following.
-----------------------
Mar 18 02:22:46 jupiter bootpd[25831]: ioctl: Invalid argument
Mar 18 02:22:54 jupiter bootpd[25838]: bootpd 2.4 #1.17.213.3: Thu Oct 23 19:47:23 GMT 1997
Mar 18 02:22:54 jupiter bootpd[25838]: ioctl: Invalid argument
Mar 18 02:22:54 jupiter inetd[1489]: bootps/udp: Exit status 1
Mar 18 02:22:55 jupiter above message repeats 25 times
Mar 18 02:22:54 jupiter syslog: received short packet from 101.95.0.1
-----------------------
I will attach the full syslog!
any suggestions as to what is going on would be appreciated!
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2003 03:53 AM
03-19-2003 03:53 AM
Re: receiving bootp/ioctl errors in syslog... what to do?
you need to install patch PHNE_19241 for hpux11.0
If you are not using bootp then you can comment out the entry in /etc/inetd.conf file so that those messages do not arise.
#bootps dgram udp wait root /usr/lbin/bootpd bootpd
Then re-read the configuration file using
#/usr/sbin/inetd -c
Thanks
If you are not using bootp then you can comment out the entry in /etc/inetd.conf file so that those messages do not arise.
#bootps dgram udp wait root /usr/lbin/bootpd bootpd
Then re-read the configuration file using
#/usr/sbin/inetd -c
Thanks
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP