New installation on SUSE Linux
A new 11.70 install on SUSE Linux failed with two separate errors: "DISK INITIALIZATION ABORTED: potential instance overwrite detected" and a listener error -25572 "Network driver cannot bind a name to the port" (plus a misleading "fatal error in shared memory initialization"). Respondents explained the first is fixed by setting FULL_DISK_INIT to 1 in the ONCONFIG and rerunning oninit -i (the server resets it to 0), and the second points to sqlhosts/DBSERVERNAME, /etc/services or /etc/hosts problems or a port already in use. The poster found a typo in /etc/hosts; after fixing it and setting FULL_DISK_INIT the instance came up quiescent, though the listener/bind error still appeared and was not fully explained. Side advice: stop using onmonitor, as it is being retired.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
'oninit -ivy' force-initializes the root dbspace/disk; the advising message itself warns to be careful not to accidentally trash a production server, since the check being overridden exists specifically to prevent overwriting an existing instance.
oninit -ivy FULL_DISK_INIT=1
Advisory only — not a substitute for testing in a non-production environment first.
I'm putting a new installation of Informix 11.7 on SUSE Linux, and I'm having
trouble with initializing shared memory. I've done the 'onit -i', and it looks
like it build my root chunk. Here is the error I get when I go into onmonitor,
and try to initialize shared memory. I know it sounds like my hosts or
sqlhosts file is messed up, but would the 'oninit -i' work if they were messed
up?
14:03:25 listener-thread: err = -25572: oserr = 13: errstr = : Network driver
cannot bind a name to the port.
System error = 13.
14:03:25 sql_listener: ASF_LISTEN failed
14:03:25 Attempting to bring listener thread down.
14:03:26 DISK INITIALIZATION ABORTED: potential instance overwrite detected.
To disable this check, set FULL_DISK_INIT to 1 in your config file and retry.
14:03:26 oninit: Fatal error in shared memory initialization
14:03:26 IBM Informix Dynamic Server Stopped.
Looks like two separate issues to me. The Network issue should not keep
shared memory from coming up unless you are using that connection to
actually connect to the server. So if cxtcp works and that is your
INFORMIXSERVER, and it's another connection like carsitcp that is not
working, shared memory still should come up.
The other issue looks like it does not want to overwrite a previous
instance unless you confirm it in the config file.
Thank you,
Jim Goldrick
System Admin
(573) 979-9079
jgoldrick@judsonu.edu
Reminder: Judson University IT will never ask for your password or other
personal information over email.
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
JOHN CALLICOTTE
Sent: Monday, January 07, 2013 4:03 PM
To: ids@iiug.org
Subject: New installation on SUSE Linux [29210]
I'm putting a new installation of Informix 11.7 on SUSE Linux, and I'm
having
trouble with initializing shared memory. I've done the 'onit -i', and it
looks
like it build my root chunk. Here is the error I get when I go into
onmonitor,
and try to initialize shared memory. I know it sounds like my hosts or
sqlhosts file is messed up, but would the 'oninit -i' work if they were
messed
up?
14:03:25 listener-thread: err = -25572: oserr = 13: errstr = : Network
driver
cannot bind a name to the port.
System error = 13.
14:03:25 sql_listener: ASF_LISTEN failed
14:03:25 Attempting to bring listener thread down.
14:03:26 DISK INITIALIZATION ABORTED: potential instance overwrite
detected.
To disable this check, set FULL_DISK_INIT to 1 in your config file and
retry.
14:03:26 oninit: Fatal error in shared memory initialization
14:03:26 IBM Informix Dynamic Server Stopped.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
There are two separate, independent problems diagnosed:
On Mon, Jan 7, 2013 at 2:02 PM, JOHN CALLICOTTE
<john.callicotte@ottawa.edu>wrote:
> I'm putting a new installation of Informix 11.7 on SUSE Linux, and I'm
> having
> trouble with initializing shared memory. I've done the 'onit -i', and it
> looks
> like it build my root chunk. Here is the error I get when I go into
> onmonitor,
> and try to initialize shared memory. I know it sounds like my hosts or
> sqlhosts file is messed up, but would the 'oninit -i' work if they were
> messed
> up?
>
> 14:03:25 listener-thread: err = -25572: oserr = 13: errstr = : Network
> driver
> cannot bind a name to the port.
> System error = 13.
> 14:03:25 sql_listener: ASF_LISTEN failed
> 14:03:25 Attempting to bring listener thread down.
>
This indicates a problem with the sqlhosts file or DBSERVERNAME or
DBSERVERALIASES entries in the ONCONFIG file.
> 14:03:26 DISK INITIALIZATION ABORTED: potential instance overwrite
> detected.
> To disable this check, set FULL_DISK_INIT to 1 in your config file and
> retry.
>
This indicates that IDS detected that the disk space was previously used by
another instance of IDS. You need to do as it says and set the ONCONFIG
parameter FULL_DISK_INIT to 1. When the server has initialized the disk,
it will update it to 0 again, so that you can't accidentally (or
deliberately) reinitialize the instance with 'oninit -i' until you re-edit
the ONCONFIG file.
> 14:03:26 oninit: Fatal error in shared memory initialization
>
> 14:03:26 IBM Informix Dynamic Server Stopped.
>
The 'fatal error in shared memory initialization' message is a legacy red
herring; it means that something went wrong during system startup, and the
specifics are the two problems outlined above (not shared memory per se).
--
Jonathan Leffler <jonathan.leffler@gmail.com> #include <disclaimer.h>
Guardian of DBD::Informix - v2011.0612 - http://dbi.perl.org
"Blessed are we who can laugh at ourselves, for we shall never cease to be
amused."
--047d7b66f515669c5304d2ba1be2
Hi,
please post your environment (INFORMIXSERVER) and sqlhosts file here.
If you previously initialized instance with your onconfig file, Informix
changed
FULL_DISK_INIT onconfig parameter to 0 - this can be rason for message
DISK INITIALIZATION ABORTED. You should change FULL_DISK_INIT to value 1.
HTH
Hrvoje
On 7.1.2013. 23:02, JOHN CALLICOTTE wrote:
> I'm putting a new installation of Informix 11.7 on SUSE Linux, and I'm having
> trouble with initializing shared memory. I've done the 'onit -i', and it
looks
> like it build my root chunk. Here is the error I get when I go into
onmonitor,
> and try to initialize shared memory. I know it sounds like my hosts or
> sqlhosts file is messed up, but would the 'oninit -i' work if they were
messed
> up?
>
> 14:03:25 listener-thread: err = -25572: oserr = 13: errstr = : Network driver
> cannot bind a name to the port.
> System error = 13.
> 14:03:25 sql_listener: ASF_LISTEN failed
> 14:03:25 Attempting to bring listener thread down.
> 14:03:26 DISK INITIALIZATION ABORTED: potential instance overwrite detected.
> To disable this check, set FULL_DISK_INIT to 1 in your config file and retry.
>
> 14:03:26 oninit: Fatal error in shared memory initialization
>
> 14:03:26 IBM Informix Dynamic Server Stopped.
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
Here is my sqlhosts file:
ksotinfx01 onsoctcp ksotinfx01 istartrain2
ksotinfx01_shm onipcshm ksotinfx01 ksotinfx01
istartrain onsoctcp ksotinfx01 istartrain
I'm confused by the istartrain2 in the first line, but I am copying another
config file over from our production server, and it works over there.
I changed the FULL_DISK_INIT to 1, and tried it again, but it still failed:
16:13:49 listener-thread: err = -25572: oserr = 13: errstr = : Network driver
cannot bind a name to the port.
System error = 13.
16:13:49 sql_listener: ASF_LISTEN failed
16:13:49 Attempting to bring listener thread down.
16:13:51 Value of FULL_DISK_INIT has been changed to 0.
16:14:29 IBM Informix Dynamic Server Initialized -- Complete Disk Initialized.
16:14:29 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed
in DBSPACETEMP: 'temp0'
16:14:29 Dataskip is now OFF for all dbspaces
16:14:29 Checkpoint Completed: duration was 0 seconds.
16:14:29 Mon Jan 7 - loguniq 1, logpos 0x1b8, timestamp: 0x77 Interval: 2
16:14:29 Maximum server connections 0
16:14:29 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 1,
Plog used 6, Llog used 1
16:14:29 Quiescent Mode
16:14:40 ASF Echo-Thread Server: asfcode = -25582: oserr = 0: errstr = :
Network connection is broken.
Hello,
you should look for istattrain2 and istartrain in /etc/services
(i.e. grep istartran /etc/services)
This should give you port numbers for both services.
Now, you shoul look if any other app is already using these ports:
(i.e. netstat -ant | grep _PORT_NUMBER_)
If some other app is using this port, Informix can't use it.
You can reconfigure other app or reconfigure Informix to use
other port(s)
HTH
Hrvoje
On 7.1.2013. 23:18, JOHN CALLICOTTE wrote:
> Here is my sqlhosts file:
>
> ksotinfx01 onsoctcp ksotinfx01 istartrain2
> ksotinfx01_shm onipcshm ksotinfx01 ksotinfx01
> istartrain onsoctcp ksotinfx01 istartrain>
> I'm confused by the istartrain2 in the first line, but I am copying another
> config file over from our production server, and it works over there.
>
> I changed the FULL_DISK_INIT to 1, and tried it again, but it still failed:
>
> 16:13:49 listener-thread: err = -25572: oserr = 13: errstr = : Network driver
> cannot bind a name to the port.
> System error = 13.
> 16:13:49 sql_listener: ASF_LISTEN failed
> 16:13:49 Attempting to bring listener thread down.
> 16:13:51 Value of FULL_DISK_INIT has been changed to 0.
> 16:14:29 IBM Informix Dynamic Server Initialized -- Complete Disk
Initialized.
> 16:14:29 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed
>
> in DBSPACETEMP: 'temp0'
> 16:14:29 Dataskip is now OFF for all dbspaces
> 16:14:29 Checkpoint Completed: duration was 0 seconds.
> 16:14:29 Mon Jan 7 - loguniq 1, logpos 0x1b8, timestamp: 0x77 Interval: 2
>
> 16:14:29 Maximum server connections 0
> 16:14:29 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 1,
> Plog used 6, Llog used 1
>
> 16:14:29 Quiescent Mode
> 16:14:40 ASF Echo-Thread Server: asfcode = -25582: oserr = 0: errstr = :
> Network connection is broken.
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
And if you have hostname and servicename in sqlhosts file, then please
post /etc/services and /etc/hosts
as well (or hostname resolution)
Hrvoje
On 7.1.2013. 23:02, JOHN CALLICOTTE wrote:
> I'm putting a new installation of Informix 11.7 on SUSE Linux, and I'm having
> trouble with initializing shared memory. I've done the 'onit -i', and it
looks
> like it build my root chunk. Here is the error I get when I go into
onmonitor,
> and try to initialize shared memory. I know it sounds like my hosts or
> sqlhosts file is messed up, but would the 'oninit -i' work if they were
messed
> up?
>
> 14:03:25 listener-thread: err = -25572: oserr = 13: errstr = : Network driver
> cannot bind a name to the port.
> System error = 13.
> 14:03:25 sql_listener: ASF_LISTEN failed
> 14:03:25 Attempting to bring listener thread down.
> 14:03:26 DISK INITIALIZATION ABORTED: potential instance overwrite detected.
> To disable this check, set FULL_DISK_INIT to 1 in your config file and retry.
>
> 14:03:26 oninit: Fatal error in shared memory initialization
>
> 14:03:26 IBM Informix Dynamic Server Stopped.
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
Yes, I carefully looked to make sure, and did the grep as well to verify. No other ports are using the ones they're assigned to.
I found a typo in my /etc/hosts file. How embarrassing. However, I'm not sure it worked. Here is what I got in my log: 16:30:44 IBM Informix Dynamic Server Version 11.70.FC4 Software Serial Number AAA#B000000 16:30:44 listener-thread: err = -25572: oserr = 13: errstr = : Network driver cannot bind a name to the port. System error = 13. 16:30:44 sql_listener: ASF_LISTEN failed 16:30:44 Attempting to bring listener thread down. 16:30:44 Value of FULL_DISK_INIT has been changed to 0. 16:31:23 IBM Informix Dynamic Server Initialized -- Complete Disk Initialized. 16:31:23 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed in DBSPACETEMP: 'temp0' 16:31:23 Dataskip is now OFF for all dbspaces 16:31:23 Checkpoint Completed: duration was 0 seconds. 16:31:23 Mon Jan 7 - loguniq 1, logpos 0x3e0, timestamp: 0xc9 Interval: 2 16:31:23 Maximum server connections 0 16:31:23 Checkpoint Statistics - Avg. Txn Block Time 0.289, # Txns blocked 1, Plog used 9, Llog used 1 16:31:23 Quiescent Mode 16:31:34 ASF Echo-Thread Server: asfcode = -25582: oserr = 0: errstr = : Network connection is broken.
Am I reading this incorrectly?
You state you have done an oninit -i Which has built you rootdbs space.
Normally this command also brings the DB engine up to quiescent mode.
Then you say you are having issues with onmonitor initializing the shared
memory ( remember that oninit -i will have done the initialization of
shared memory )
The errors listed say the port that you connect to the DB on is currently
in use, and that the database was initialized and can not be initialized
again without resetting the flag that prevents re-initialization of an
instance.
What was the outcome of the oninit -i ? did it error. is the system in
quiescent mode or is it down?
George.
From: "JOHN CALLICOTTE" <john.callicotte@ottawa.edu>
To: ids@iiug.org
Date: 01/07/2013 04:03 PM
Subject: New installation on SUSE Linux [29210]
Sent by: ids-bounces@iiug.org
I'm putting a new installation of Informix 11.7 on SUSE Linux, and I'm
having
trouble with initializing shared memory. I've done the 'onit -i', and it
looks
like it build my root chunk. Here is the error I get when I go into
onmonitor,
and try to initialize shared memory. I know it sounds like my hosts or
sqlhosts file is messed up, but would the 'oninit -i' work if they were
messed
up?
14:03:25 listener-thread: err = -25572: oserr = 13: errstr = : Network
driver
cannot bind a name to the port.
System error = 13.
14:03:25 sql_listener: ASF_LISTEN failed
14:03:25 Attempting to bring listener thread down.
14:03:26 DISK INITIALIZATION ABORTED: potential instance overwrite
detected.
To disable this check, set FULL_DISK_INIT to 1 in your config file and
retry.
14:03:26 oninit: Fatal error in shared memory initialization
14:03:26 IBM Informix Dynamic Server Stopped.
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
Well, I think it's in quiescent mode now. If I go to onmonitor, and check the status that's what it looks like. I think I may be good.
Is this normal or non-root installation? Do you have firewall? Can you post result of: grep istartrain /etc/services grep ksotinfx02 /etc/hosts netstat -at | grep istartrain Hrvoje On 7.1.2013. 23:32, JOHN CALLICOTTE wrote: > I found a typo in my /etc/hosts file. How embarrassing. However, I'm not sure > it worked. Here is what I got in my log: > > 16:30:44 IBM Informix Dynamic Server Version 11.70.FC4 Software Serial Number > AAA#B000000 > 16:30:44 listener-thread: err = -25572: oserr = 13: errstr = : Network driver > cannot bind a name to the port. > System error = 13. > 16:30:44 sql_listener: ASF_LISTEN failed > 16:30:44 Attempting to bring listener thread down. > 16:30:44 Value of FULL_DISK_INIT has been changed to 0. > 16:31:23 IBM Informix Dynamic Server Initialized -- Complete Disk Initialized. > 16:31:23 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed > > in DBSPACETEMP: 'temp0' > 16:31:23 Dataskip is now OFF for all dbspaces > 16:31:23 Checkpoint Completed: duration was 0 seconds. > 16:31:23 Mon Jan 7 - loguniq 1, logpos 0x3e0, timestamp: 0xc9 Interval: 2 > > 16:31:23 Maximum server connections 0 > 16:31:23 Checkpoint Statistics - Avg. Txn Block Time 0.289, # Txns blocked 1, > Plog used 9, Llog used 1 > > 16:31:23 Quiescent Mode > 16:31:34 ASF Echo-Thread Server: asfcode = -25582: oserr = 0: errstr = : > Network connection is broken. > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > >
Forget about onmonitor, it will eventually go away, and it doesn't support
most of the current server configuration variables properly. Go into the
onconfig file and set FULL_DISK_INIT to 1, save, and run:
oninit -ivy
This is because either there was an older server defined using that root
chunk, or a attempt to initialize the server failed after writing to the
root chunk, so just be careful you are not accidentally trashing a
production server. Don't know about the networking error though.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
other organization with which I am associated either explicitly,
implicitly, or by inference. Neither do those opinions reflect those of
other individuals affiliated with any entity with which I am affiliated nor
those of the entities themselves.
On Mon, Jan 7, 2013 at 4:02 PM, JOHN CALLICOTTE
<john.callicotte@ottawa.edu>wrote:
> I'm putting a new installation of Informix 11.7 on SUSE Linux, and I'm
> having
> trouble with initializing shared memory. I've done the 'onit -i', and it
> looks
> like it build my root chunk. Here is the error I get when I go into
> onmonitor,
> and try to initialize shared memory. I know it sounds like my hosts or
> sqlhosts file is messed up, but would the 'oninit -i' work if they were
> messed
> up?
>
> 14:03:25 listener-thread: err = -25572: oserr = 13: errstr = : Network
> driver
> cannot bind a name to the port.
> System error = 13.
> 14:03:25 sql_listener: ASF_LISTEN failed
> 14:03:25 Attempting to bring listener thread down.
> 14:03:26 DISK INITIALIZATION ABORTED: potential instance overwrite
> detected.
> To disable this check, set FULL_DISK_INIT to 1 in your config file and
> retry.
>
> 14:03:26 oninit: Fatal error in shared memory initialization
>
> 14:03:26 IBM Informix Dynamic Server Stopped.
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--14dae934041f4c4cad04d2bb7fce
On Mon, Jan 7, 2013 at 3:50 PM, Art Kagel <art.kagel@gmail.com> wrote: > Forget about onmonitor, it will eventually go away, and it doesn't support > most of the current server configuration variables properly. > Note that 'eventually' is going to be sooner rather than later. Obviously, ON-Monitor will continue to exist in currently released versions of Informix (for as long as they are supported), but you should start planning on the assumption that future major releases of Informix will not have ON-Monitor any more. (And you should never try running an old version of ON-Monitor against a newer version of Informix!) -- Jonathan Leffler <jonathan.leffler@gmail.com> #include <disclaimer.h> Guardian of DBD::Informix - v2011.0612 - http://dbi.perl.org "Blessed are we who can laugh at ourselves, for we shall never cease to be amused." --047d7b62440c5d7e3904d2bbc71d
Related threads
- HELP- database won't start !!
- Network driver cannot bind a name to the port.
- Solaris 8, IDSWE 7.31, WARNING: Network Down
- Error 25572 using ESQL/Cobol
- Identically named instances, different hosts