Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- Technology and Support
- DevNet Hub
- DevNet Collaboration
- Collaboration Knowledge Base
- WebEx Social version 3.3 SR1 upgrade issue
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
146
Views
0
Helpful
0
Comments
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 01-24-2014 05:18 PM
This document was generated from CDN thread
Created by: Sergey Svishenko on 08-06-2013 07:02:54 AM
Hello!
I have upgrade my Cisco WebEx Social portal from version 3.1 SR3 to version 3.3 SR1. After I have done this I can't login to my Application server with my AD credentials. I see error - "Authentication failed. Try again."
Also in Cisco WebEx Social Director server in Health category I see following errors for Application, Worker and Message server:
CRITICAL: STATUS filesystems: status failed (1) for /var/monit/check_filesystems.sh. Error: Disk '/mnt/auto/cms' is NOT writable: 1
How can I resolve all these errors?
Subject: RE: WebEx Social version 3.3 SR1 upgrade issue
Replied by: Ratnadeep Ray on 10-06-2013 01:33:27 AM
Hi Sergey,
Regarding the Authentication failure, can you please try the following:
* From Director run the command below to execute service puppet debug on all nodes.#sudo salt '*' cmd.run 'echo $(service puppet debug)'
* If you are authenticating against AD try resetting the password.
* Disable/Enable App and Cache node.
* Check the logs for any error message.
* Check /opt/cisco/quad/tomcat/webapps/ROOT/WEB-INF/classes/portal-ext.properties for corruption.
Let me know what you find from the above.
Regarding the Health issue related to /var/monit/check_filesystems.sh, this generally happens when the mount is not accessible which makes monit report red flag to Nagios. Nagios will then report this service as 'Critical' on Director Health page/API. So if possible please create the mounts once again. FYI, any modifications made to monit config are overwritten on next puppet run, upgrade or reboot.
Hope this helps.
Regards,
Ratnadeep.
Subject: RE: WebEx Social version 3.3 SR1 upgrade issue
Replied by: Sergey Svishenko on 10-06-2013 02:11:44 AM
Hello!
Regarding Authentication failure - yes I use AD, in audit log file from my Application server I see, that authentication source=null after upgrade, but before upgrade authentication source = "DC_IPaddress".
I have attached audit log (upgrade time after 10:00 in log).
How can I check /opt/cisco/quad/tomcat/webapps/ROOT/WEB-INF/classes/portal-ext.properties for corruptions?
Regarding NFS mount on all servers (Application, Director, Message, Working) I see that NFS shares are mounded:
[admin@ws-app ~]$ cd /mnt/auto/
[admin@ws-app auto]$ ls -l
total 4
drwxrwxr-x 9 quad quad 4096 2013-06-08 10:40 cms
[admin@ws-app auto]$ cd ./cms/
[admin@ws-app cms]$ ls -l
total 28
drwxrwxr-x 3 quad quad 4096 2012-09-10 10:49 document_library
drwxrwxr-x 11 quad quad 4096 2013-06-08 10:39 email_templates
drwxrwxr-x 22 quad quad 4096 2013-06-04 13:38 images
drwxrwxr-x 18 quad quad 4096 2013-03-27 09:46 inboundmail
drwxrwxr-x 2 quad quad 4096 2013-06-08 10:40 media_gallery
drwxrwxr-x 2 quad quad 4096 2013-06-08 10:40 post_attachment
drwxrwxr-x 2 quad quad 4096 2013-06-10 07:00 tunnel-upload
[admin@ws-app cms]$
[admin@ws-director ~]$ cd /mnt/auto/
[admin@ws-director auto]$ ls -l
total 4
drwxrwxr-x 2 quad quad 4096 2012-08-21 07:06 backup
[admin@ws-director auto]$ cd ./backup/
[admin@ws-director backup]$ ls -l
total 0
[admin@ws-director backup]$
[admin@ws-message ~]$ cd /mnt/auto/
[admin@ws-message auto]$ ls -l
total 4
drwxrwxr-x 3 activemq quad 4096 2012-09-10 10:14 jms
[admin@ws-message auto]$ cd ./jms/
[admin@ws-message jms]$ ls -l
total 4
drwxrwxr-x 4 activemq quad 4096 2012-09-12 10:11 data
[admin@ws-message jms]$
[admin@ws-worker ~]$ cd /mnt/auto/
[admin@ws-worker auto]$ ls -l
total 4
drwxrwxr-x 9 quad quad 4096 2013-06-08 10:40 cms
[admin@ws-worker auto]$ cd ./cms/
[admin@ws-worker cms]$ ls -l
total 28
drwxrwxr-x 3 quad quad 4096 2012-09-10 10:49 document_library
drwxrwxr-x 11 quad quad 4096 2013-06-08 10:39 email_templates
drwxrwxr-x 22 quad quad 4096 2013-06-04 13:38 images
drwxrwxr-x 18 quad quad 4096 2013-03-27 09:46 inboundmail
drwxrwxr-x 2 quad quad 4096 2013-06-08 10:40 media_gallery
drwxrwxr-x 2 quad quad 4096 2013-06-08 10:40 post_attachment
drwxrwxr-x 2 quad quad 4096 2013-06-10 07:00 tunnel-upload
[admin@ws-worker cms]$
Subject: RE: WebEx Social version 3.3 SR1 upgrade issue
Replied by: Sergey Svishenko on 11-06-2013 12:48:03 AM
Hello!
Regarding NFS - I solved it by setting "no_root_squash" option in /etc/export file.
But authentication still does not work. If I have root access to Application role server, where can I find
AD authentication settings, I think that after upgrade this settings were been eliminated.
Subject: RE: WebEx Social version 3.3 SR1 upgrade issue
Replied by: Kalin Sheytanov on 11-06-2013 04:18:27 AM
Hello Sergey,
I beleive you should still be able to log into the app server with the built it adimistrative account, called "test"
If so, once you login you can go over and verify the LDAP auth settings.
Let us know if you need any other assistance.
Cheers,
Kalin.
Subject: RE: New Message from Kalin Sheytanov in WebEx Social Developer - Troublesho
Replied by: Sergey Svishenko on 11-06-2013 04:26:05 AM
Hello!
I can’t login with default user account test@your_company.com<mailto:test@your_company.com> too.
From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Tuesday, June 11, 2013 1:18 PM
To: cdicuser@developer.cisco.com
Subject: New Message from Kalin Sheytanov in WebEx Social Developer - Troubleshooting: RE: WebEx Social version 3.3 SR1 upgrade issue
Kalin Sheytanov has created a new message in the forum "Troubleshooting": -------------------------------------------------------------- Hello Sergey,
I beleive you should still be able to log into the app server with the built it adimistrative account, called "test"
If so, once you login you can go over and verify the LDAP auth settings.
Let us know if you need any other assistance.
Cheers,
Kalin.
--
To respond to this post, please click the following link: http://developer.cisco.com/web/webexsocial-developer/forums/-/message_boards/view_message/16074700 or simply reply to this email.
Subject: RE: WebEx Social version 3.3 SR1 upgrade issue
Replied by: Kalin Sheytanov on 11-06-2013 05:26:21 AM
Hi Sergey,
Please do the following:
Provide a snippet from the app server logs at the time of the login failre, bot for the admin(test) user and for a regular ldap user.
As a side node:
WxS 3.3 uses a new password encryption mechanism and existing passwords are re-encrypted as part of the data migration process. Lets verify if data migration from 3.1 to 3.3 has completed successfully. To do so:
- look for the string "UpgradeProcessSprint20_3_3.doUpgrade(): Complete..." in the app server logs at the time of the upgrade.
- Run the following sql query agains the WxS database and give us the output:
select modifieddate,buildnumber from quaddb.release_;
- Check for any errors in the appserver/worker logs during the time when data migration took place.
Best Regards,
Kalin.
Subject: RE: WebEx Social version 3.3 SR1 upgrade issue
Replied by: Sergey Svishenko on 11-06-2013 06:27:42 AM
Subject: RE: WebEx Social version 3.3 SR1 upgrade issue
Replied by: Sergey Svishenko on 11-06-2013 06:35:40 AM
Hello!
I have attached all log files:
ws-app_appserver.zip - log files with migration process, I see that string "UpgradeProcessSprint20_3_3.doUpgrade(): Complete" is there.
2013_06_11.zip - today's log files, I try login with s.svishenko@cti.ru and test@your_company.com username.
On which server and in which folder should I run command "select modifieddate,buildnumber from quaddb.release_"
Subject: RE: WebEx Social version 3.3 SR1 upgrade issue
Replied by: Haydeh Dejbakhsh on 11-06-2013 11:40:57 AM
Hello Sergey,
When Kalin stated:
- Run the following sql query agains the WxS database and give us the output:
select modifieddate,buildnumber from quaddb.release_;
He wanted you to do the following:
ssh to RDBM node as admin
sudo su - oracle
sqlplus / as sysdba
SQL>
Then when you are at SQL> prompt do:
SQL> select modifieddate,buildnumber from quaddb.release_;
Post the output of the Query for him.
Thanks, /heidi
Subject: RE: WebEx Social version 3.3 SR1 upgrade issue
Replied by: Sergey Svishenko on 11-06-2013 01:01:43 PM
Hello!
Here is output:
SQL> select modifieddate,buildnumber from quaddb.release_;
MODIFIEDDATE---------------------------------------------------------------------------
BUILDNUMBER
-----------
10-SEP-12 10.43.51.000000 AM 20005
10-JUN-13 03.27.39.476000 PM 5206
Created by: Sergey Svishenko on 08-06-2013 07:02:54 AM
Hello!
I have upgrade my Cisco WebEx Social portal from version 3.1 SR3 to version 3.3 SR1. After I have done this I can't login to my Application server with my AD credentials. I see error - "Authentication failed. Try again."
Also in Cisco WebEx Social Director server in Health category I see following errors for Application, Worker and Message server:
CRITICAL: STATUS filesystems: status failed (1) for /var/monit/check_filesystems.sh. Error: Disk '/mnt/auto/cms' is NOT writable: 1
How can I resolve all these errors?
Subject: RE: WebEx Social version 3.3 SR1 upgrade issue
Replied by: Ratnadeep Ray on 10-06-2013 01:33:27 AM
Hi Sergey,
Regarding the Authentication failure, can you please try the following:
* From Director run the command below to execute service puppet debug on all nodes.#sudo salt '*' cmd.run 'echo $(service puppet debug)'
* If you are authenticating against AD try resetting the password.
* Disable/Enable App and Cache node.
* Check the logs for any error message.
* Check /opt/cisco/quad/tomcat/webapps/ROOT/WEB-INF/classes/portal-ext.properties for corruption.
Let me know what you find from the above.
Regarding the Health issue related to /var/monit/check_filesystems.sh, this generally happens when the mount is not accessible which makes monit report red flag to Nagios. Nagios will then report this service as 'Critical' on Director Health page/API. So if possible please create the mounts once again. FYI, any modifications made to monit config are overwritten on next puppet run, upgrade or reboot.
Hope this helps.
Regards,
Ratnadeep.
Subject: RE: WebEx Social version 3.3 SR1 upgrade issue
Replied by: Sergey Svishenko on 10-06-2013 02:11:44 AM
Hello!
Regarding Authentication failure - yes I use AD, in audit log file from my Application server I see, that authentication source=null after upgrade, but before upgrade authentication source = "DC_IPaddress".
I have attached audit log (upgrade time after 10:00 in log).
How can I check /opt/cisco/quad/tomcat/webapps/ROOT/WEB-INF/classes/portal-ext.properties for corruptions?
Regarding NFS mount on all servers (Application, Director, Message, Working) I see that NFS shares are mounded:
[admin@ws-app ~]$ cd /mnt/auto/
[admin@ws-app auto]$ ls -l
total 4
drwxrwxr-x 9 quad quad 4096 2013-06-08 10:40 cms
[admin@ws-app auto]$ cd ./cms/
[admin@ws-app cms]$ ls -l
total 28
drwxrwxr-x 3 quad quad 4096 2012-09-10 10:49 document_library
drwxrwxr-x 11 quad quad 4096 2013-06-08 10:39 email_templates
drwxrwxr-x 22 quad quad 4096 2013-06-04 13:38 images
drwxrwxr-x 18 quad quad 4096 2013-03-27 09:46 inboundmail
drwxrwxr-x 2 quad quad 4096 2013-06-08 10:40 media_gallery
drwxrwxr-x 2 quad quad 4096 2013-06-08 10:40 post_attachment
drwxrwxr-x 2 quad quad 4096 2013-06-10 07:00 tunnel-upload
[admin@ws-app cms]$
[admin@ws-director ~]$ cd /mnt/auto/
[admin@ws-director auto]$ ls -l
total 4
drwxrwxr-x 2 quad quad 4096 2012-08-21 07:06 backup
[admin@ws-director auto]$ cd ./backup/
[admin@ws-director backup]$ ls -l
total 0
[admin@ws-director backup]$
[admin@ws-message ~]$ cd /mnt/auto/
[admin@ws-message auto]$ ls -l
total 4
drwxrwxr-x 3 activemq quad 4096 2012-09-10 10:14 jms
[admin@ws-message auto]$ cd ./jms/
[admin@ws-message jms]$ ls -l
total 4
drwxrwxr-x 4 activemq quad 4096 2012-09-12 10:11 data
[admin@ws-message jms]$
[admin@ws-worker ~]$ cd /mnt/auto/
[admin@ws-worker auto]$ ls -l
total 4
drwxrwxr-x 9 quad quad 4096 2013-06-08 10:40 cms
[admin@ws-worker auto]$ cd ./cms/
[admin@ws-worker cms]$ ls -l
total 28
drwxrwxr-x 3 quad quad 4096 2012-09-10 10:49 document_library
drwxrwxr-x 11 quad quad 4096 2013-06-08 10:39 email_templates
drwxrwxr-x 22 quad quad 4096 2013-06-04 13:38 images
drwxrwxr-x 18 quad quad 4096 2013-03-27 09:46 inboundmail
drwxrwxr-x 2 quad quad 4096 2013-06-08 10:40 media_gallery
drwxrwxr-x 2 quad quad 4096 2013-06-08 10:40 post_attachment
drwxrwxr-x 2 quad quad 4096 2013-06-10 07:00 tunnel-upload
[admin@ws-worker cms]$
Subject: RE: WebEx Social version 3.3 SR1 upgrade issue
Replied by: Sergey Svishenko on 11-06-2013 12:48:03 AM
Hello!
Regarding NFS - I solved it by setting "no_root_squash" option in /etc/export file.
But authentication still does not work. If I have root access to Application role server, where can I find
AD authentication settings, I think that after upgrade this settings were been eliminated.
Subject: RE: WebEx Social version 3.3 SR1 upgrade issue
Replied by: Kalin Sheytanov on 11-06-2013 04:18:27 AM
Hello Sergey,
I beleive you should still be able to log into the app server with the built it adimistrative account, called "test"
If so, once you login you can go over and verify the LDAP auth settings.
Let us know if you need any other assistance.
Cheers,
Kalin.
Subject: RE: New Message from Kalin Sheytanov in WebEx Social Developer - Troublesho
Replied by: Sergey Svishenko on 11-06-2013 04:26:05 AM
Hello!
I can’t login with default user account test@your_company.com<mailto:test@your_company.com> too.
From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Tuesday, June 11, 2013 1:18 PM
To: cdicuser@developer.cisco.com
Subject: New Message from Kalin Sheytanov in WebEx Social Developer - Troubleshooting: RE: WebEx Social version 3.3 SR1 upgrade issue
Kalin Sheytanov has created a new message in the forum "Troubleshooting": -------------------------------------------------------------- Hello Sergey,
I beleive you should still be able to log into the app server with the built it adimistrative account, called "test"
If so, once you login you can go over and verify the LDAP auth settings.
Let us know if you need any other assistance.
Cheers,
Kalin.
--
To respond to this post, please click the following link: http://developer.cisco.com/web/webexsocial-developer/forums/-/message_boards/view_message/16074700 or simply reply to this email.
Subject: RE: WebEx Social version 3.3 SR1 upgrade issue
Replied by: Kalin Sheytanov on 11-06-2013 05:26:21 AM
Hi Sergey,
Please do the following:
Provide a snippet from the app server logs at the time of the login failre, bot for the admin(test) user and for a regular ldap user.
As a side node:
WxS 3.3 uses a new password encryption mechanism and existing passwords are re-encrypted as part of the data migration process. Lets verify if data migration from 3.1 to 3.3 has completed successfully. To do so:
- look for the string "UpgradeProcessSprint20_3_3.doUpgrade(): Complete..." in the app server logs at the time of the upgrade.
- Run the following sql query agains the WxS database and give us the output:
select modifieddate,buildnumber from quaddb.release_;
- Check for any errors in the appserver/worker logs during the time when data migration took place.
Best Regards,
Kalin.
Subject: RE: WebEx Social version 3.3 SR1 upgrade issue
Replied by: Sergey Svishenko on 11-06-2013 06:27:42 AM
Kalin Sheytanov:Hi Sergey,
Please do the following:
Provide a snippet from the app server logs at the time of the login failre, bot for the admin(test) user and for a regular ldap user.
As a side node:
WxS 3.3 uses a new password encryption mechanism and existing passwords are re-encrypted as part of the data migration process. Lets verify if data migration from 3.1 to 3.3 has completed successfully. To do so:
- look for the string "UpgradeProcessSprint20_3_3.doUpgrade(): Complete..." in the app server logs at the time of the upgrade.
- Run the following sql query agains the WxS database and give us the output:
select modifieddate,buildnumber from quaddb.release_;
- Check for any errors in the appserver/worker logs during the time when data migration took place.
Best Regards,
Kalin.
Subject: RE: WebEx Social version 3.3 SR1 upgrade issue
Replied by: Sergey Svishenko on 11-06-2013 06:35:40 AM
Hello!
I have attached all log files:
ws-app_appserver.zip - log files with migration process, I see that string "UpgradeProcessSprint20_3_3.doUpgrade(): Complete" is there.
2013_06_11.zip - today's log files, I try login with s.svishenko@cti.ru and test@your_company.com username.
On which server and in which folder should I run command "select modifieddate,buildnumber from quaddb.release_"
Subject: RE: WebEx Social version 3.3 SR1 upgrade issue
Replied by: Haydeh Dejbakhsh on 11-06-2013 11:40:57 AM
Hello Sergey,
When Kalin stated:
- Run the following sql query agains the WxS database and give us the output:
select modifieddate,buildnumber from quaddb.release_;
He wanted you to do the following:
ssh to RDBM node as admin
sudo su - oracle
sqlplus / as sysdba
SQL>
Then when you are at SQL> prompt do:
SQL> select modifieddate,buildnumber from quaddb.release_;
Post the output of the Query for him.
Thanks, /heidi
Subject: RE: WebEx Social version 3.3 SR1 upgrade issue
Replied by: Sergey Svishenko on 11-06-2013 01:01:43 PM
Hello!
Here is output:
SQL> select modifieddate,buildnumber from quaddb.release_;
MODIFIEDDATE---------------------------------------------------------------------------
BUILDNUMBER
-----------
10-SEP-12 10.43.51.000000 AM 20005
10-JUN-13 03.27.39.476000 PM 5206
Labels:
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:
Customers Also Viewed These Support Documents