HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Error on bringing up IFS Jserv on reboot - works w...
Operating System - HP-UX
1835886
Members
6654
Online
110086
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-03-2003 10:13 AM
03-03-2003 10:13 AM
Error on bringing up IFS Jserv on reboot - works without reboot.
We have Oracle IFS and Apache Jserv 1.1 running on a HP-UX 11.0 box. We have scripts to bring up IFS and they work when you bring IFS up manually. The same script is called on startup but it fails to bring up Jserv.
Error in jserv.log is:
apj12: can not connect to host 127.0.0.1:13138
This error message does not appear when we startup ifs at root prompt.
Any suggestions? I don't think we are bringing up anything on this port.
On using lsof on a working system, the foll process runs on port 13138
PA_RISC2. 2909 ora9i 21u inet 0x48883668 0t0 TCP localhost:13138 (LISTEN)
Any ideas? Thanks.
Geetha.
Error in jserv.log is:
apj12: can not connect to host 127.0.0.1:13138
This error message does not appear when we startup ifs at root prompt.
Any suggestions? I don't think we are bringing up anything on this port.
On using lsof on a working system, the foll process runs on port 13138
PA_RISC2. 2909 ora9i 21u inet 0x48883668 0t0 TCP localhost:13138 (LISTEN)
Any ideas? Thanks.
Geetha.
hercules
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-03-2003 09:52 AM
03-03-2003 09:52 AM
Re: Error on bringing up IFS Jserv on reboot - works without reboot.
I am curious where in the startup chain that you are trying to start this. In other words, is it starting in /sbin/rc1.d or rc2.d etc? You may be starting it too early in the init process before networking or Oracle is fully is fully started.
If it has wheels or a skirt, you can't afford it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-03-2003 10:22 AM
03-03-2003 10:22 AM
Re: Error on bringing up IFS Jserv on reboot - works without reboot.
This is another example of poor oracle testing of their scripts.
There is probably an environment or terminal type problem.
The user that starts these guys up has one environment, the startup user has less.
As the user that owns the oracle apps.
env > /tmp/env.ias
stty -a > /tmp/env.ias
now in the startup scripts
env > /tmp/env.ias.startup
stty -a > /tmp/env.ias.startup
Restart, compare files
Modify the startup scripts to make the environments, including TERM variable as close as possible.
For some reason, this line in our startup script fixed the problem, Oracle has no idea why.
# /usr/bin/ps -ef | /usr/bin/grep rwmts60 > /tmp/rep6ifromscript.data
Adding these three lines to our startup script gave us better diagnostics and helped resolve the problem.
set -x
TERM=vt220
export TERM
The whole thing is however quite mysterious.
SEP
There is probably an environment or terminal type problem.
The user that starts these guys up has one environment, the startup user has less.
As the user that owns the oracle apps.
env > /tmp/env.ias
stty -a > /tmp/env.ias
now in the startup scripts
env > /tmp/env.ias.startup
stty -a > /tmp/env.ias.startup
Restart, compare files
Modify the startup scripts to make the environments, including TERM variable as close as possible.
For some reason, this line in our startup script fixed the problem, Oracle has no idea why.
# /usr/bin/ps -ef | /usr/bin/grep rwmts60 > /tmp/rep6ifromscript.data
Adding these three lines to our startup script gave us better diagnostics and helped resolve the problem.
set -x
TERM=vt220
export TERM
The whole thing is however quite mysterious.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-03-2003 10:30 AM
03-03-2003 10:30 AM
Re: Error on bringing up IFS Jserv on reboot - works without reboot.
John,
We are starting it up in rc3.d - we too were suspicious of that.
Steven,
Thanks. We forced the root environment on this script by doing a su - root -c oraifs. As root was the user that brought up IFS, but it didn't help.
I'll try it out your suggestions - will keep you posted.
Geetha.
We are starting it up in rc3.d - we too were suspicious of that.
Steven,
Thanks. We forced the root environment on this script by doing a su - root -c oraifs. As root was the user that brought up IFS, but it didn't help.
I'll try it out your suggestions - will keep you posted.
Geetha.
hercules
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