| Author |
Message
|
| arifndc |
 Posted: Tue Sep 15, 2009 9:09 pm Post subject: An error has occurred reading an INI file |
 |
|
Novice
Joined: 15 Sep 2009
Posts: 24
|
I m using 6.0.2.3. I have two QueueManagers already that are working. Before some time i added the following line in qm.ini file of one of the QueueManager
Channels:
MaxChannels=700
MaxActiveChannels=600
TCP:
KeepAlive = Yes
ListenerBacklog=700
Now i m creating a new Queue Manager with crtmqm QM1 but the error is occuring *"An error has occurred reading an INI file"*. I even tried by removing these change form qm.ini but same error is occuring.
-Arif |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Sep 16, 2009 6:03 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
If you have the problem creating a new qmgr, nothing in the old qmgrs qm.ini file is relevant. Check mqs.ini in the /var/mqm directory...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jeevan |
| Posted: Wed Sep 16, 2009 9:10 pm Post subject: Re: An error has occurred reading an INI file |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| arifndc wrote: |
I m using 6.0.2.3. I have two QueueManagers already that are working. Before some time i added the following line in qm.ini file of one of the QueueManager
Channels:
MaxChannels=700
MaxActiveChannels=600
TCP:
KeepAlive = Yes
ListenerBacklog=700
Now i m creating a new Queue Manager with crtmqm QM1 but the error is occuring *"An error has occurred reading an INI file"*. I even tried by removing these change form qm.ini but same error is occuring.
-Arif |
While creating a new queue manager, mq does not write to qm.ini file of the existing queue manager. However, it writes to mqs.ini file. So, this INI file indicates the mqs.ini file not the qm.ini file of your other queue manager.
If you have backed up the mqs.ini file, restore. Try to read it by any editor and see whether you can open it or not. If you can not read it, and do not have a backup, you may need to recreate this file. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Sep 16, 2009 9:54 pm Post subject: Re: An error has occurred reading an INI file |
|
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
| jeevan wrote: |
While creating a new queue manager, mq does not write to qm.ini file of the existing queue manager. However, it writes to mqs.ini file. |
It doesn't write to it, it reads it.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| gunter |
| Posted: Wed Sep 16, 2009 10:45 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2004
Posts: 307
Location: Germany, Frankfurt
|
| Quote: |
| It doesn't write to it, it reads it. |
There is an entry for every queuemanager in it, so it writes it, too.
_________________
Gunter Jeschawitz
IBM Certified System Administrator - Websphere MQ, 5.3 |
|
| Back to top |
|
|
| arifndc |
| Posted: Thu Sep 17, 2009 12:06 am Post subject: An error has occurred reading an INI file |
|
|
Novice
Joined: 15 Sep 2009
Posts: 24
|
i have attached mqs.ini and qm.in (i which i made the changes)
can anyone help why there is error reading these.
-Arif |
|
| Back to top |
|
|
| arifndc |
| Posted: Thu Sep 17, 2009 12:12 am Post subject: |
|
|
Novice
Joined: 15 Sep 2009
Posts: 24
|
I have copied the contents of both the files can any body help me.
==========mqs.ini================
AllQueueManagers:
#********************************************************************#
#* The path to the qmgrs directory, below which queue manager data *#
#* is stored *#
#********************************************************************#
DefaultPrefix=/var/mqm
ClientExitPath:
ExitsDefaultPath=/var/mqm/exits
ExitsDefaultPath64=/var/mqm/exits64
LogDefaults:
LogPrimaryFiles=3
LogSecondaryFiles=2
LogFilePages=1024
LogType=CIRCULAR
LogBufferPages=0
LogDefaultPath=/var/mqm/log
DefaultQueueManager:
Name=mq.test
QueueManager:
Name=mq.test
Prefix=/var/mqm
Directory=mq!test
QueueManager:
Name=mq2.test
Prefix=/var/mqm
Directory=mq2!test
============mq.ini================
#*******************************************************************#
ExitPath:
ExitsDefaultPath=/var/mqm/exits/
ExitsDefaultPath64=/var/mqm/exits64/
#* *#
#* *#
Log:
LogPrimaryFiles=20
LogSecondaryFiles=15
LogFilePages=1024
LogType=CIRCULAR
LogBufferPages=0
LogPath=/var/mqm/log/mq!test/
LogWriteIntegrity=TripleWrite
Service:
Name=AuthorizationService
EntryPoints=13
ServiceComponent:
Service=AuthorizationService
Name=MQSeries.UNIX.auth.service
Module=/usr/mqm/lib64/amqzfu
ComponentDataSize=0
Channels:
MaxChannels=700
MaxActiveChannels=600
TCP:
KeepAlive = Yes
ListenerBacklog=700
-Arif |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Sep 17, 2009 12:19 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| arifndc wrote: |
TCP:
KeepAlive = Yes
ListenerBacklog=700 |
That's the only thing that catches my eye, as it should be KeepAlive=Yes (no spaces).
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| arifndc |
| Posted: Thu Sep 17, 2009 12:39 am Post subject: |
|
|
Novice
Joined: 15 Sep 2009
Posts: 24
|
I have removed the spaces but same error is still comming
can you tell me what services should be restarted. two existing queue manager were already stoppd i just start and stop that queue manager of that ini file i have removed the spaces from.
I thing if qm.ini i creating problem then queue manager should not be started and stop normally. m i right ????
-Arif |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Sep 17, 2009 12:49 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
1. Is the name of the queue manager you are trying to create appearing in the mqs.ini file?
2. Are the ownership/permissions correct for the mqs.ini file?
3. Is the directory structure for that queue manager being created?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| arifndc |
| Posted: Thu Sep 17, 2009 1:15 am Post subject: |
|
|
Novice
Joined: 15 Sep 2009
Posts: 24
|
1- No. it is showing the queue manager created already.
2- yes mqs.ini file is under mqm owner ship. its permission is 777
3- When i run the crtmqm QM1 command. structure is created but when command end and shows error messages structures removed (i think i creates structure temporary and when error occured it is removes)
What should i do now ???
-Arif |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Sep 17, 2009 1:32 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Apologies if I am misinterpreting/misunderstanding your post, but:
| arifndc wrote: |
| 1- No. it is showing the queue manager created already. |
Are you stating that the entry for the queue manager you are trying to create already exists in the mqs.ini file, or, do you mean that it is only showing your two existing queue managers?
Check also the permissions and file space available in both log and qmgrs directories - it's possible the qm.ini file is not being created for the queue manager, and therefore cannot be read, or is being created but is inaccessible.
EDIT: Additional question - are any FDC files being created?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| gunter |
| Posted: Thu Sep 17, 2009 3:42 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2004
Posts: 307
Location: Germany, Frankfurt
|
| Quote: |
| its permission is 777 |
??? execute permission on a ini file ???
Thats not set by mq.
Check if mqs.ini is still a unix file and check the end of file, too.
Maybe someone opend and saved the file via samba or ftp in a windows editor.
_________________
Gunter Jeschawitz
IBM Certified System Administrator - Websphere MQ, 5.3 |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Sep 17, 2009 4:12 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
| gunter wrote: |
| Quote: |
| It doesn't write to it, it reads it. |
There is an entry for every queuemanager in it, so it writes it, too. |
Thanks for correcting me. It reads it to create the new QM, and then writes to it to record the new QM. Forgot about that second part.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Thu Sep 17, 2009 7:37 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3265
Location: London, ON Canada
|
Hi,
A long time ago, I once had a similar error ("An error has occurred reading an INI file") for a different MQ process on Solaris WMQ v5.3 (probably CSD 3).
It took a lot of work to figure it out. Basically, we had a monitoring task that cron launched once a minute. The Unix shell script did a "cat mqs.ini" each time it ran to get a list of queue managers. I changed it to get the queue manager information from a different source and then the problem went away.
Strange but true.
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
|
|
