cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2420
Views
15
Helpful
11
Replies

Cisco Meeting Place Express 2.1.1.2 and not working anymore

benacquis
Level 1
Level 1

Hello, we currently have cisco meeting place express 2.1.1.2; however are now having issues with it.  We are unable to dial to the internal extension that was previously working to login to the meetings and only get a busy signal everytime. Furthermore, whenever someone tries to schedule a new meeting via the web form, it says "request to server timed out. please try again".

I tried reaching out to Cisco TAC support; however it's no longer a supported item and am looking for assistance here.  The TAC engineer was able to help assist with updating the system clock; however I believe the problems started happening after we updated the clock and rebooted the server.  Now we are unable to schedule and attend any meetings (busy signal everytime) at all.  I tried restarting the server itself as well as via the command line.  I also now see an error during CLI restart, which I have listed directly below:

Stopping MeetingPlace SNMP/R:                              [  OK  ]
Stopping mpe-tomcat-main: bash: /root/.bashrc: Permission denied
                                                           [  OK  ]
Stopping mpe-tomcat-securewebservices: bash: /root/.bashrc: Permission denied
                                                           [  OK  ]
Shutting down breeze:                                      [  OK  ]
Shutting down fmsmaster:                                   [  OK  ]
Shutting down fmsadmin:                                    [  OK  ]
Stopping MeetingPlace application: /etc/init.d/mpx_app: line 264:  4955 Segmentation fault      (core dumped) ${shutdown_bin} ${shutdown_arg_1} ${shutdown_arg_2} ${shutdown_arg_3} >>${non_verbose_shutdown_output} 2>&1
                                                           [FAILED]
    ERROR: returncode = 139
Stopping MeetingPlace License Manager:                     [  OK  ]
Stopping MeetingPlace database:                            [  OK  ]
Stopping MeetingPlace Java RMI: Shutting down RMI Registry:

                                                           [  OK  ]
----------
Stopping Cisco MeetingPlace Express:                       [  OK  ]

Starting MeetingPlace Java RMI: Starting RMI Registry:
starting daemon
mpxadmin
                                                           [  OK  ]
Starting MeetingPlace database:                            [  OK  ]
Starting MeetingPlace License Manager:                     [  OK  ]
Starting MeetingPlace application:                         [  OK  ]
    already running
Starting breeze:                                           [  OK  ]
Starting fmsmaster:                                        [  OK  ]
Starting fmsadmin:                                         [  OK  ]
Starting mpe-tomcat-main: bash: /root/.bashrc: Permission denied
                                                           [  OK  ]

Both the admin and user web interfaces work on the home pages, but can't seem to schedule any new meetings or login to any existing ones, with busy signal as well. Anyone have any ideas? We need assistance with this ASAP since it's our voice collaboration solution.  Thanks in advance for any help.                  

11 Replies 11

dpetrovi
Cisco Employee
Cisco Employee

Hello,

As you said, MPE is not supported by TAC any longer, and without reviewing the logs and checking the system out it is hard to see what is going on. Per these messages it doesn't look good.

I would advise you to copy the backup files from the system (located in /db/backup/compressed_backup) to your machine, rebuild the system to the exisitng version level (I assume it is 2.1.1.2), apply the hotfix you currently have on the system (the latest one is HF41), copy the preserved backup files back to the newly installed server, and then perform a restore from backups located locally on the server (with the appropriate date): 

http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace_Express,_Release_2.x_--_How_to_Back_Up,_Archive,_and_Restore_Data

I hope this will help you.

-Dejan

thanks for the reply Dejan. We are going to look into upgrading our MP to something else in the very near future, since there is no easy fix.

Thanks again and regards,

Ben

Amlesh Sengar
Level 1
Level 1

Hi Ben,

Can you please forward the "df -h" from the CLI interface.  

It is possible that disk space is 100% and thus we see  request time out.

Thanks,

Amlesh

Hi Amlesh,

Thank you for your suggestion. Actually one of the TAC engineers was kind enough to help me look into a few things for about an hour or so.  We did in fact confirm that there is about 40% space left available disk space.  We also noticed that the server was rebooting itself about every 10-15 mins for some reason (didnt notice it before). We looked around as much as we could; however with MPE no longer being supported, we really couldnt figure out the solution accordingly.

Seems like we are just going to use a different solution, since upgrading to a new version of MP requires new hardware, etc as well.

Thanks, again for response and regards,

Ben

I'm also having the same issue with my customer, version 2.1.1.2:

[root@county-mp1 afs]# df -h

Filesystem            Size  Used Avail Use% Mounted on

/dev/cciss/c0d0p1     5.8G  3.8G  1.8G  68% /

/dev/cciss/c0d0p6     3.9G  3.9G     0 100% /common

/dev/cciss/c0d0p2     7.7G  5.8G  1.6G  80% /db

/dev/cciss/c0d0p9     251M  8.3M  230M   4% /grub

/dev/cciss/c0d0p7      37G   33M   35G   1% /mpx-record

/dev/cciss/c0d0p5     4.9G  3.1G  1.6G  67% /opt

/dev/cciss/c0d0p3     5.8G   33M  5.5G   1% /partB

none                 1004M   23M  982M   3% /dev/shm

I spent some time going through the Disk Optimization guide but didn't make a dent.

http://www.cisco.com/en/US/products/ps6533/products_tech_note09186a0080c13ffe.shtml

I also followed up on another thread following the suggestions

https://supportforums.cisco.com/message/3170782#3170782

I don't really know where else to look to delete since this release is no longer supported. Any advice would be appreciated. Thanks.

Jared

Hi Jared,

   You have  /common which is 100% full.

  Please try to find large files from that directory and create free space.

You can use command:   find /common -size +10000k  to find large files/logs in that folder.

Thanks,

Amlesh

Amlesh,

Here is the pertinent output:

/common/log/taos-log-a/core/core.1947.11.ConfSchd.1183266069

/common/log/taos-log-a/core/core.1837.6.gyromain.bin.1183266161

/common/log/taos-log-a/core/core.1859.6.cpgs.1183266206

/common/log/taos-log-a/core/core.1951.11.ConfSchd.1184475669

/common/log/taos-log-a/core/core.1946.11.ConfSchd.1185685269

/common/log/taos-log-a/core/core.1836.6.gyromain.bin.1185685332

/common/log/taos-log-a/core/core.1880.6.cca.1185685452

/common/log/taos-log-a/core/core.1858.6.cpgs.1185685452

/common/log/taos-log-a/core/core.1950.11.ConfSchd.1185771671

/common/log/taos-log-a/core/core.1863.6.cpgs.1185771865

/common/log/taos-log-a/core/core.1884.6.cca.1185771865

/common/log/taos-log-a/core/core.1991.6.nmpagent.1185771865

/common/log/taos-log-a/core/core.1950.11.ConfSchd.1185858067

/common/log/taos-log-a/core/core.1952.11.ConfSchd.1188018079

/common/log/taos-log-a/core/core.1969.11.ConfSchd.1188190869

/common/log/taos-log-a/core/core.2008.6.vui.1188190988

/common/log/taos-log-a/core/core.2029.6.nmpagent.1188190988

/common/log/taos-log-a/core/core.1998.6.poclient.1188190988

/common/log/taos-log-a/core/core.1970.11.ConfSchd.1189227671

/common/log/taos-log-a/core/core.1862.6.gyromain.bin.1189227762

/common/log/taos-log-a/core/core.1883.6.cpgs.1189227807

/common/log/taos-log-a/core/core.1952.11.ConfSchd.1189918866

/common/log/taos-log-a/core/core.1952.11.ConfSchd.1190005281

/common/log/taos-log-a/core/core.1952.11.ConfSchd.1190178068

/common/log/taos-log-a/core/core.1886.6.cca.1190178237

/common/log/taos-log-a/core/core.2012.6.nmpagent.1190178237

/common/log/taos-log-a/core/core.1952.11.ConfSchd.1191906070

/common/log/taos-log-a/core/core.1843.6.gyromain.bin.1191906162

/common/log/taos-log-a/core/core.1886.6.cca.1191906248

/common/log/taos-log-a/core/core.1865.6.cpgs.1191906248

/common/log/taos-log-a/core/core.1950.11.ConfSchd.1192424479

/common/log/taos-log-a/core/core.1842.6.gyromain.bin.1192424571

/common/log/taos-log-a/core/core.1863.6.cpgs.1192424613

/common/log/taos-log-a/core/core.1951.11.ConfSchd.1192597270

/common/log/taos-log-a/core/core.1969.11.ConfSchd.1192683669

/common/log/taos-log-a/core/core.1903.6.cca.1192683817

/common/log/taos-log-a/core/core.1951.11.ConfSchd.1193029270

/common/log/taos-log-a/core/core.1842.6.gyromain.bin.1193029360

/common/log/taos-log-a/core/core.1864.6.cpgs.1193029400

/common/log/taos-log-a/core/core.1952.11.ConfSchd.1193720467

/common/log/taos-log-a/core/core.1843.6.gyromain.bin.1193720565

/common/log/taos-log-a/core/core.1864.6.cpgs.1193720610

/common/log/taos-log-a/core/core.1952.11.ConfSchd.1195452071

/common/log/taos-log-a/core/core.1843.6.gyromain.bin.1195452170

/common/log/taos-log-a/core/core.1864.6.cpgs.1195452213

/common/log/taos-log-a/core/core.1952.11.ConfSchd.1196834481

/common/log/taos-log-a/core/core.1952.11.ConfSchd.1197007273

/common/log/taos-log-a/core/core.1842.6.gyromain.bin.1197007371

/common/log/taos-log-a/core/core.1864.6.cpgs.1197007413

/common/log/taos-log-a/core/core.1952.11.ConfSchd.1198044080

/common/log/taos-log-a/core/core.1843.6.gyromain.bin.1198044184

/common/log/taos-log-a/core/core.1842.6.gyromain.bin.1199858530

My understanding is these core files are crash dumps and are safe to delete?

Jared

Hi Jared,

You are correct, these are old crash files.

Please try to increase the file size and check if we can narrow down large files.

find /common -size +100000k

Amlesh,

[root@county-mp1 root]# find /common -size +100000k

/common/rpm-archive/1.0.0.7-1/os.tar.gz

/common/cisco/MPE/DBbackup/FullBackup-1.2.0.111

Jared

Hi Jared,

You can create some free space by deleting the crash logs as indicated in output earlier.

Thanks,

Amlesh

Amlesh,

That brought the common partition to 28%. Thanks for your assistance!

Jared

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: