GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Problems - FTP INBOUND NOT WORKING! HELP!
Operating System - HP-UX
1847860
Members
3233
Online
104021
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
Forums
Discussions
back
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
06-11-2001 10:37 AM
06-11-2001 10:37 AM
tail syslog.log
Jun 11 13:20:53 esuunix1 vmunix: WARNING: modpath: DLKM is not initialized
Jun 11 13:23:22 esuunix1 vmunix: WARNING: ioctl: DLKM is not initialized
Jun 11 13:19:11 esuunix1 ftpd[6504]: User rmueller: Login incorrect
Jun 11 13:23:22 esuunix1 ftpd[7152]: pam_acct_mgmt:General Commercial Security error. 134217759
Jun 11 13:23:22 esuunix1 vmunix: WARNING: modpath: DLKM is not initialized
Jun 11 13:23:22 esuunix1 above message repeats 2 times
Jun 11 13:23:22 esuunix1 ftpd[7152]: User rmueller: Login incorrect
Jun 11 13:23:29 esuunix1 ftpd[7152]: FTP session closed
Jun 11 13:25:18 esuunix1 tftpd[6118]: Timeout (no requests in 10 minutes)
Jun 11 13:23:22 esuunix1 ftpd[7152]: User rmueller: Login incorrect
Jun 11 13:20:53 esuunix1 vmunix: WARNING: modpath: DLKM is not initialized
Jun 11 13:23:22 esuunix1 vmunix: WARNING: ioctl: DLKM is not initialized
Jun 11 13:19:11 esuunix1 ftpd[6504]: User rmueller: Login incorrect
Jun 11 13:23:22 esuunix1 ftpd[7152]: pam_acct_mgmt:General Commercial Security error. 134217759
Jun 11 13:23:22 esuunix1 vmunix: WARNING: modpath: DLKM is not initialized
Jun 11 13:23:22 esuunix1 above message repeats 2 times
Jun 11 13:23:22 esuunix1 ftpd[7152]: User rmueller: Login incorrect
Jun 11 13:23:29 esuunix1 ftpd[7152]: FTP session closed
Jun 11 13:25:18 esuunix1 tftpd[6118]: Timeout (no requests in 10 minutes)
Jun 11 13:23:22 esuunix1 ftpd[7152]: User rmueller: Login incorrect
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2001 11:37 AM
06-11-2001 11:37 AM
Solution
Here's a cut/paste of a something that may help:
=================================
PROBLEM
The following messages occur in the /var/adm/syslog/syslog.log file and dmesg
output.
WARNING: modpath: DLKM is not initialized
WARNING: modpath: DLKM is not initialized
WARNING: modadm: DLKM is not initialized
WARNING: modadm: DLKM is not initialized
RESOLUTION
This is usally the result of not running kmupdate after kernel generation.
The following should correct the issue (this will require a reboot of the
system)
1. Change directories to /stand/build:
cd /stand/build
2. Create a new system file to be used for kernel generation:
/usr/lbin/sysadm/system_prep -s system
3. Create the new kernel:
mk_kernel -s ./system
4. Run kmupdate to update the Dynamically Linked Kernel Module information:
kmupdate /stand/build/vmunix_test
5. Reboot the system:
shutdown -r 0 (don't use reboot !!!)
Regards,
Rita
=================================
PROBLEM
The following messages occur in the /var/adm/syslog/syslog.log file and dmesg
output.
WARNING: modpath: DLKM is not initialized
WARNING: modpath: DLKM is not initialized
WARNING: modadm: DLKM is not initialized
WARNING: modadm: DLKM is not initialized
RESOLUTION
This is usally the result of not running kmupdate after kernel generation.
The following should correct the issue (this will require a reboot of the
system)
1. Change directories to /stand/build:
cd /stand/build
2. Create a new system file to be used for kernel generation:
/usr/lbin/sysadm/system_prep -s system
3. Create the new kernel:
mk_kernel -s ./system
4. Run kmupdate to update the Dynamically Linked Kernel Module information:
kmupdate /stand/build/vmunix_test
5. Reboot the system:
shutdown -r 0 (don't use reboot !!!)
Regards,
Rita
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 2026 Hewlett Packard Enterprise Development LP