[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

852.0. "VCS problem - DUPMBX" by KERNEL::MILLSS (All good things must come to an end...) Tue Jul 04 1995 16:55

Now that the VCS conference is write-locked I have no choice but to post this
question here because I can't find the answer anywhere else !

My customer is running VCS V1.4 and VMS V5.5-2. When they try to start up VCS
the VCS$IODL process fails with a "DUPMBX, duplicate mailbox" error.

They have tried rebooting, but the error remains.

I have searched high and low for an explanation of the DUPMBX error with no
luck. I *know* it stands for duplicate mailbox, but what does it *mean* !?!?

Any help or advice would be greatly appreciated.

Thanks.

Simon R. Mills
South UK CSC
T.RTitleUserPersonal
Name
DateLines
852.1BACHUS::WILLEMSGGeert Willems MCS-BelgiumWed Jul 05 1995 15:3525
    
    	Hi Simon,
    
    
    
        DUPMBX = Duplicate mailbox
    
          Severity: Error
    
          Explanation: During initialization, when VCS$IODL tried to create
          its mailbox, it discovered the system already had a mailbox by that
          name. The usual cause is another VCS$IODL already running on the
          system.
    
          User Action: Find the other VCS$IODL and stop it before trying to
          run another, or use VCS$STARTUP.COM which automatically checks and
          stops another VCS$IODL.
    
    
    	What do you find in the different VCS logfiles ?
    
    	Rgds,
    
    	Geert
    
852.2KERNEL::MILLSSAll good things must come to an end...Wed Jul 05 1995 16:368
Thanks, Geert, but shouldn't rebooting the system kill the extra process,
anyway? I can't get through to the customer at the moment (phone is constantly
busy (his, not mine!)). The only thing I can think of is that they're calling
VCS$STARTUP twice, but that should result in only one VCS$IODL, shouldn't it ?

Regards,

Simon
852.3exCSC32::BUTTERWORTHGun Control is a steady hand.Wed Jul 05 1995 19:1226
    >Thanks, Geert, but shouldn't rebooting the system kill the extra
    >process, anyway? 
    
    Indeed, unless they are doing something screwy during system startup.
    They may have some other process running the IODL image but with a 
    different process name.
    
    To see if this is the case do the following:
    
    $ ana/system
    SDA> set output proc.log
    SDA> sho summ/image
    SDA> exit
    $ search  proc.log IODL
    
    
    >I can't get through to the customer at the moment (phone is constantly
    >busy (his, not mine!)). The only thing I can think of is that they're
    >calling VCS$STARTUP twice, but that should result in only one VCS$IODL,
    >shouldn't it ?
    
    Yes it would, unless the RESTART paramater was specified on the second
    call it will fail because the process already exists.
    
    Regards,
         dan