Agent Primary Server Failover

Hi All
Can someone tell me how the adaptive agent decides to choose which server to connect to?, we have two primary servers in our zone and it always connects to the same one, even when the first primary server is switched off they agent authentication will fail.
We moved the sybase database from one server to another and still the agent will not authenticate. So we added a DNS round robin so that the second server had the same DNS name as the primary and that kind of works (slow access) but seems like a very dodgy way of getting things to work from the second server.
So just to clarify:-
Server1 (First Primary On) When this is on all works well.
Server1 (First Primary Down) The Second Zone Member Server2 does not work even when it holds the database, the agent still tries to connect to Server1.
We make a DNS Round Robin so that Server1&Server2 resolve to the DNS of Server1.ourcomany.com it appears to work but seems a bit of a cowboy fix to me, is this really the way we would recover from a primary crash if we did not use remote databases.

I'm guessing the failure to the 2nd Server is failing when the first server
is down because that is your Certificate Authority.
Are you using an Internal or External Cert?
Craig Wilson - MCNE, MCSE, CCNA
Novell Support Forums Volunteer Sysop
Novell does not officially monitor these forums.
Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
"106666" <[email protected]> wrote in message
news:[email protected]..
>
> Hi All
>
>
> Can someone tell me how the adaptive agent decides to choose which
> server to connect to?, we have two primary servers in our zone and it
> always connects to the same one, even when the first primary server is
> switched off they agent authentication will fail.
>
> We moved the sybase database from one server to another and still the
> agent will not authenticate. So we added a DNS round robin so that the
> second server had the same DNS name as the primary and that kind of
> works (slow access) but seems like a very dodgy way of getting things
> to work from the second server.
>
> So just to clarify:-
>
> Server1 (First Primary On) When this is on all works well.
>
> Server1 (First Primary Down) The Second Zone Member Server2 does not
> work even when it holds the database, the agent still tries to connect
> to Server1.
>
> We make a DNS Round Robin so that Server1&Server2 resolve to the DNS of
> Server1.ourcomany.com it appears to work but seems a bit of a cowboy fix
> to me, is this really the way we would recover from a primary crash if
> we did not use remote databases.
>
>
> --
> 106666
> ------------------------------------------------------------------------
> 106666's Profile: http://forums.novell.com/member.php?userid=6795
> View this thread: http://forums.novell.com/showthread.php?t=314104
>

Similar Messages

Communication between the primary server the gateway server

hallo
Can I set the directional communication between the primary server the gateway server, so it feels by the following example?
And if so how?
Agent
à GW
ß GW
ß MS
*Agent communicates with GW1 and reported it
*GW SEND report to GW2
*GW2 Send the the data to MS
thanks
<o:p></o:p>
אם תגובתי פתרה את בעייתך - לחץ/י, על "סמן כתשובה" ליד סימן ה V הירוק.

Hi,
As far as I know, Gateways dont talk to each other. Why you need two GW, with one GW and report to your management servers, this way should work.
Here is a similar thread for your reference:
https://social.technet.microsoft.com/Forums/systemcenter/en-US/323d5aab-bad4-4c23-b096-27a62757ae31/communications-between-2-gateway-servers-and-2-ms?forum=operationsmanagerdeployment
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

How to find out the primary and failover DNS name

Hi;
This sounds very stupid, but could some one please tell me how to find out the name/dns name of the primary and failover server without using the CDS console.
any help is appreciated

Is this what you want?
$ /usr/lib/ldap/ldap_cachemgr -g
cachemgr configuration:
server debug level 0
server log file "/var/ldap/cachemgr.log"
number of calls to ldapcachemgr 12729
cachemgr cache data statistics:
Configuration refresh information:
Previous refresh time: 2005/08/07 23:54:59
Next refresh time: 2005/08/08 00:55:00
Server information:
Previous refresh time: 2005/08/14 15:15:00
Next refresh time: 2005/08/15 03:15:00
server: ldap1.example.com, status: UP
server: ldap2.example.com, status: UP
server: ldap3.example.com, status: UP
Cache data information:
Maximum cache entries: 256
Number of cache entries: 0
Gary

Upgraded ZENworks Primary Server Will Not Refresh

Good Afternoon,
I recently upgraded our primary server from ZENworks 11.2-11.3a.
The upgrade procedure completed with no errors. However, the server will not refresh it's status in the ZENworks Control Center. Control Center continues to report the server as 11.2.0.0. The UI of the Control Center is upgraded. The agent continues to push back the next contact with server time without updating the last contact with server time
Things I have tried:
-doing a manual refresh through control center gives a "Connection Failed" error
-doing a manual refresh with zac ref completes successfully but does not update anything
-cleared the agent cache using zac cc
Any help would be appreciated.
Thank you very much!

Try the solution you find in this thread:
http://forums.novell.com/novell-prod...nt-management/
zenworks/configuration-management/zcm-11/zcm11-agent-deployment-linux/45
5516-how-recover-lost-trust-relationship-zone-configuration-between-linu
x-zcm-agent-primary-zone-server-running-same-machine.html
W. Prindl
wpico wrote:
>
>CRAIGDWILSON;2331318 Wrote:
>> This is because the Agent Service (Servers have an agent too)
>>cannot talk to the zone.
>>
>> Normally the only time this is noticed is during a "System Update",
>> since this is one of the few times the failure would be noted.
>>
>> However, the 11.3.0 Upgrade would not have relied on the agent
>>server and since you upgraded from 11.2.0, another ISO install, it
>>is quite possible there were always some issues there.
>>
>> "zac retr" might help, but it also may be wise to open an SR so
>>they can
>> see what is wrong and not just have you poking and prodding your
>>only primary.
>>
>>
>> On 8/28/2014 4:46 PM, wpico wrote:
>> >
>> > nop1983;2331309 Wrote:
>> >> wpico wrote:
>> >>
>> >>>
>> >>> Good Afternoon,
>> >>>
>> >>> I recently upgraded our primary server from ZENworks
>>11.2-11.3a. >>>
>> >>> The upgrade procedure completed with no errors. However, the
>> server
>> >>> will not refresh it's status in the ZENworks Control Center.
>> Control
>> >>> Center continues to report the server as 11.2.0.0. The UI of
>>the >>> Control Center is upgraded. The agent continues to push
>>back the next
>> >>> contact with server time without updating the last contact with
>> server
>> >>> time
>> >>>
>> >>> Things I have tried:
>> >>> -doing a manual refresh through control center gives a
>>"Connection >>> Failed" error
>> >>> -doing a manual refresh with zac ref completes successfully but
>> does
>> >>> not update anything
>> >>> -cleared the agent cache using zac cc
>> >>>
>> >>> Any help would be appreciated.
>> >>>
>> >>> Thank you very much!
>> >>
>> >> Only one server?
>> >> Sounds like the agent could have lost the trust, somehow... The
>> update
>> >> went fine?
>> >>
>> >> --
>> >> Niels
>> >> I have always liked... Cowabunga!
>> >>
>> >> If you find this post helpful, please show your appreciation by
>> clicking
>> >> on the star below.
>> >> A member must be logged in before s/he can assign reputation
>>points. >
>> > Completed with no errors, The log file was all green.
>> >
>> >
>>
>>
>> --
>> Going to Brainshare 2014?
>> http://www.brainshare.com
>> Use Registration Code "nvlcwilson" for $300 off!
>>
>>
>> Craig Wilson - MCNE, MCSE, CCNA
>> Novell Technical Support Engineer
>>
>> Novell does not officially monitor these forums.
>>
>> Suggestions/Opinions/Statements made by me are solely my own.
>> These thoughts may not be shared by either Novell or any rational
>>human.
>
>When I run zac retr I get, "Failed to re-establish trust with zone"

How to restore standby from primary after failover.

HI we have a dr setup but the standby is provided archives through an application not the datagaurd.
So for applying application patch I cant switchover the database.
I have to shutdown the primary database and apply failover to the standby database to apply patch.
Can you please tell how can I restore my standby database to actual primary after failover.
As our actual activity will be in 2 weeks time. We want to apply patch on saturday.
DR DRILL is on 8th nov.

Your earlier statement "Can you please tell how can I restore my standby database to actual primary after failover"
means something different from "SO have to restore from cold backup of primary database"
What you seem to want is a procedure to recreate the Standby from a Backup of the Pirmary. (ie FROM Primary TO Standby).
You haven't specified your Oracle Version. DG has been available since 9i (was even backported to 8i) but I will presume that you are using 9i
You should follow the same process as used for the first creation of the standby, except that you don't have to repeat some of the setup steps (listener, tnsnames etc)
http://download.oracle.com/docs/cd/B10501_01/server.920/a96653/create_ps.htm#63563
Hemant K Chitale
http://hemantoracledba.blogspot.com

Service Accounts for Reporting Service in SQL Server Failover Cluster setup

I am setting up 2 Report Services (SSRS) in SQL Failover Clustering (Version: 2012SP1) on Windows 2012, as part of scale out architecture.
There are 2 options to configure the service account for SSRS:
Option 1) Using domain accounts, as what I have done for DB Engine and SQL Agent.
Option 2) accept the default, which is virtual account for SSRS. Per documentation URL:
http://msdn.microsoft.com/en-us/library/ms143504.aspx
which is the recommended one? is it option 2?
There is security note on above URL as well, but does not clearly mention that option 1 is not recommended.
Security Note: Always run SQL Server services by using the lowest possible user rights. Use a MSA or virtual account when possible. When MSA and virtual accounts are not possible, use a specific low-privilege user account or domain account instead
of a shared account for SQL Server services. Use separate accounts for different SQL Server services. Do not grant additional permissions to the SQL Server service account or the service groups. Permissions will be granted through group membership or granted
directly to a service SID, where a service SID is supported.
Thanks very much for your help!

Hi Luo Donghua,
In SQL Server Failover Cluster Instance, personally two options can run well. If you use the virtual account for SQL Server Reporting Service. Virtual accounts in Windows Server 2008 R2 and Windows 7 are managed local accounts that provide the features to
simplify service administration. The virtual account is auto-managed, and the virtual account can access the network in a domain environment.
Of cause, you can also use domain accounts in your clustering.
Just make sure your service account is set up here, or that it is using a proper built-in account.For more information, see:http://ermahblerg.com/2012/11/08/cluster-ssrs-in-2008/
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

How to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)

I have a scenario with the three nodes with server 2012 standard, each running an instance of SQL Server 2012 enterprise, participate in a
single Windows Server Failover Cluster (WSFC) that spans two data centers.
If the nodes in the primary data center are unavailable due to data center outage. Then how I can able to access node in the WSFC (Windows Server Failover Cluster) in the secondary disaster recovery data center automatically with some script.
I want to write script that can be able to check primary data center by pinging some IP after every 5 or 10 minutes.
If that IP is unable to respond then script can be able to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)
Can you please guide me for script writing for automatic failover in case of primary datacenter outage?

please post you question on failover clusters in the cluster forum. THey will explain how this works and point you at scipts.
You should also look in the Gallery for cluster management scripts.
¯\_(ツ)_/¯

How to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster) with scrpiting

I have a scenario with the three nodes with server 2012 standard, each running an instance of SQL Server 2012 enterprise, participate in a
single Windows Server Failover Cluster (WSFC) that spans two data centers.
If the nodes in the primary data center are unavailable due to data center outage. Then how I can able to access node in the WSFC (Windows Server Failover Cluster) in the secondary disaster recovery data center automatically with some script.
I want to write script that can be able to check primary data center by pinging some IP after every 5 or 10 minutes.
If that IP is unable to respond then script can be able to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)
Can you please guide me for script writing for automatic failover in case of primary datacenter outage?

You are trying to implement manually what should be happening automatically in the cluster. If the primary SQL Server becomes unavailable in the data center, it should fail over to the secondary SQL Server automatically. Is that not working?
You also might want to run this configuration by some SQL experts. I am not a SQL expert, but if you have both hosts in the data center in a cluster, there is no need for replication between those two nodes as they would be accessing
the database from some form of shared storage. Then it looks like you are trying to implement Always On to the DR site. I'm not sure you can mix both types of failover in a single configuration.
FYI, it would make more sense to establish a file share witness in your DR site instead of placing a third node in the data center for Node Majority quorum.
. : | : . : | : . tim

VIP still reachable even if primary server farm is down

Hi,
I want to make sure that the a VIP is not PING-able anymore when the primary server farm is down (all servers are down).
For that I have the following configuration :
serverfarm host NCL_FARM_TEST
probe NCL_PROBE_HTTP
rserver CHPAUN028 443
inservice
policy-map type loadbalance http first-match L7_POLICY_NCL_TEST_HTTP
description *** Load balancing rule for test in http mode ***
class L7_CLASS_TEST
serverfarm NCL_FARM_TEST backup NCL_REDIRECT_FARM_SORRY
compress default-method gzip
insert-http Source-IP header-value "%is"
insert-http Remote-Port header-value "%pd"
ssl-proxy client NCL_SSL_CLIENT
policy-map multi-match VIP_PROD_AND_TEST
class L4_CLASS_NCL_TEST_HTTP
loadbalance vip inservice
loadbalance policy L7_POLICY_NCL_TEST_HTTP
loadbalance vip icmp-reply active primary-inservice
nat dynamic 2 vlan 115
appl-parameter http advanced-options NCL_HTTP_PARAM
While testing this feature, I realize that the VIP is still reachable (PING), even if the server in the farm is in PROBE_FAILED status (For test, I have only one srserver in the farm).
Here is the server farm status, while PING is still possible :
CH01AC03/P-115-A# sh serverfarm NCL_FARM_TEST detail
serverfarm : NCL_FARM_TEST, type: HOST
total rservers : 1
active rservers: 0
description : *** Test Server Farm ***
state : INACTIVE
predictor : ROUNDROBIN
failaction : -
back-inservice : 0
partial-threshold : 0
num times failover : 27
num times back inservice : 28
total conn-dropcount : 0
Probe(s) :
NCL_PROBE_HTTP, type = HTTP
----------connections-----------
real weight state current total failures
---+---------------------+------+------------+----------+----------+---------
rserver: CHPAUN028
10.240.3.128:443 8 PROBE-FAILED 0 609 8
description : -
max-conns : - , out-of-rotation count : -
min-conns : -
conn-rate-limit : - , out-of-rotation count : -
bandwidth-rate-limit : - , out-of-rotation count : -
retcode out-of-rotation count : -
In the documentation, the following is written regarding the command "vip loadbalance icmp-reply active primary-inservice" it is stated that the ACE shold discard ping packets if all servers in the primary server farm are down.
I probably missed something, but what ?
Here is the service-policy status :
Policy-map : VIP_PROD_AND_TEST
Status : ACTIVE
Interface: vlan 1 115
class: L4_CLASS_NCL_TEST_HTTP
nat:
nat dynamic 2 vlan 115
curr conns : 0 , hit count : 56
dropped conns : 0
client pkt count : 809 , client byte count: 231750
server pkt count : 1262 , server byte count: 1375334
conn-rate-limit : 0 , drop-count : 0
bandwidth-rate-limit : 0 , drop-count : 0
loadbalance:
L7 loadbalance policy: L7_POLICY_NCL_TEST_HTTP
VIP ICMP Reply : ENABLED-WHEN-PRIMARY-SF-UP
VIP State: INSERVICE
Persistence Rebalance: ENABLED
curr conns : 0 , hit count : 56
dropped conns : 0
client pkt count : 809 , client byte count: 231750
server pkt count : 1262 , server byte count: 1375334
conn-rate-limit : 0 , drop-count : 0
bandwidth-rate-limit : 0 , drop-count : 0
compression:
bytes_in : 1052393
bytes_out : 309229
Compression ratio : 70.61%
Parameter-map(s):
NCL_HTTP_PARAM
Thank you for any hints,
Yves Haemmerli

Gilles,
I have effectively four diferent policy maps :
- one for PROD when the client arrives withh HTTP
- one for PROD when the client arrives with HTTPS
- one for TEST when the client arrives with HTTP
one for TEST when the client arrives with HTTPS
However, the PROD and the TEST environemnts use different server farms. I am testing the icmp-reply feature on the TEST environment. In the TEST environment, both Layer-7 policy maps use the same server farm.
Here are the four polici maps :
policy-map type loadbalance http first-match L7_POLICY_NCL_PROD_HTTP
description *** Load balancing rule for production in http mode ***
class L7_CLASS_PROD
serverfarm NCL_FARM_PROD backup NCL_REDIRECT_FARM_SORRY
insert-http Source-IP header-value "%is"
insert-http Remote-Port header-value "%pd"
ssl-proxy client NCL_SSL_CLIENT
class L7_CLASS_REDIRECT
serverfarm NCL_REDIRECT_FARM_PROD_HTTP
policy-map type loadbalance http first-match L7_POLICY_NCL_PROD_HTTPS
description *** Load balancing rule for production in https mode ***
class L7_CLASS_PROD
serverfarm NCL_FARM_PROD backup NCL_REDIRECT_FARM_SORRY
insert-http Source-IP header-value "%is"
insert-http Remote-Port header-value "%pd"
ssl-proxy client NCL_SSL_CLIENT
class L7_CLASS_REDIRECT
serverfarm NCL_REDIRECT_FARM_PROD_HTTPS
policy-map type loadbalance http first-match L7_POLICY_NCL_TEST_HTTP
description *** Load balancing rule for test in http mode ***
class L7_CLASS_TEST
serverfarm NCL_FARM_TEST backup NCL_REDIRECT_FARM_SORRY
compress default-method gzip
insert-http Source-IP header-value "%is"
insert-http Remote-Port header-value "%pd"
ssl-proxy client NCL_SSL_CLIENT
class L7_CLASS_REDIRECT
serverfarm NCL_REDIRECT_FARM_TEST_HTTP
policy-map type loadbalance http first-match L7_POLICY_NCL_TEST_HTTPS
description *** Load balancing rule for test in https mode ***
class L7_CLASS_TEST
serverfarm NCL_FARM_TEST backup NCL_REDIRECT_FARM_SORRY
insert-http Source-IP header-value "%is"
insert-http Remote-Port header-value "%pd"
ssl-proxy client NCL_SSL_CLIENT
class L7_CLASS_REDIRECT
serverfarm NCL_REDIRECT_FARM_TEST_HTTPS
Yves

Secondary DPM server does not show "protected server group" when attempting to protect primary server

Hi Guys,
I have a bit of a weird situation with DPM 2012(pre SP1). We have a primary server which is running quite happily(protects 8 SQL servers). I'm attempting to setup a secondary. When I've done this in the past with other DPM versions(this version included)
all i have to do is this following:
Install the same version of DPM on the "secondary machine"
Attach the agent on the "primary server"
Create a new protection group for everything
The catch is that I only see the following:
I can successfully protect the database of the primary server. However the secondary server cannot see any computers protected on the primary for some reason. Any ideas why this object doesn't show at all?

Hi,
At any time, was the primary DPM Server rebuilt and it's database restored ?
Can you verify that the DPMWriter service is running.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

The lease timeout between avaiability group and the Windows Server Failover Cluster has expired

Hi,
I am having some issues where I get a lease timeout from time to time. I have a Windows 2012 Failover Cluster with 2 nodes and 2 SQL 2012 Always-on Availability Groups. Both nodes
are a physical machines and each node is the primary for an AG.
From what I understand if
the HealhCheckTimeout
is exceeded without the signal exchange the lease is declared 'expired' and the SQL Server resource dll reports that the SQL Server availability group no longer 'looks alive' to the Windows cluster manager. Here are the properties I have setup
which are the default settings:
LeaseTimeout - 20000
HealthCheckTimeout - 30000
VerboseLoging - 0>
FailureConditionLevel – 3
Here are the events that occur in the Application Event Viewer:
Event ID 19407:
The lease between availability group 'AG_NAME' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover
Cluster. To determine whether the availability group is failing over correctly, check the corresponding availability group resource in the Windows Server Failover Cluster.
Event ID 35285:
The recovery LSN (120881:37533:1) was identified for the database with ID 32. This is an informational message only. No user action is required.
SQl server logs are too long to post in this box but I can send them if you request.
The AG is setup to failover automatically but it did not failover. I am trying to figure out why the lease timed out. Thanks.

From what I've been able to find out, this is due to an issue with the procedure sp_server_diagnostics. It sounds like the cluster is expecting this procedure to regularly log good status "Clean" in the log files, but the procedure is designed not
to flood the logs with "Clean" messages, so only reports changes, and does not make an entry when the last status was "Clean" and the current status is "Clean". The result is that the cluster looks to be unresponsive. However, once it initiates
the failover, the primary machine responds, since it was never really down, and the failover operation stops.
The end result is that there really never is a failover, but the database becomes unavailable for a few minutes while this is resolved.
I'm going to try setting the cluster's failure condition level to 2 (instead of 3) and see if that prevents the down time.
blogs.msdn.com/b/sql_pfe_blog/archive/2013/04/08/sql-2012-alwayson-availability-groups-automatic-failover-doesn-t-occur-or-does-it-a-look-at-the-logs.aspx

Failover clusterign... How similar do the primary and failover instance need to be in a failover cluster?

How similar do the primary and failover instance need to be in a failover cluster?
Does the number of database have to match, naming, general config etc...
Mr Shaw

In failover clustering, you use shared storage so the number of databases is irrelevant since only one node can see/access the shared storage at any given point in time. Ideally, the server configuration should be the same on all of the nodes to minimize
potential issues that may impact downtime. However, you need to consider licensing/# of CPU-cores and implementation cost, especially if you are only using the other nodes as standby. As far as licensing is concerned, the standby has to have the same or fewer
number of CPU-cores as the primary node to be covered by licensing. Besides, you don't want your standby node to be more powerful than your primary node. This is why the option to have a hybrid deployment of having a physical server as the primary node and
virtual machine for standby nodes is now supported.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Secondary Server MP is not working after primary server database up gradation.

Hi All,
Required your Help for MP Issue.
we had migrated the SQL data base in one of our Primary server, where there is 10 secondary servers are available.
7 secondary servers are working fine and remain 3 servers MP has down after the migration.
PFB the MPcontroal log.
NetBIOS_AddName(): LocalName: MP_XXX LanaNumber: 2
SMS_MP_CONTROL_MANAGER 7/8/2014 1:23:49 PM
4480 (0x1180)
RegisterWithWINS: NetBIOS_AddName(LANA=2) returned 0x0
SMS_MP_CONTROL_MANAGER 7/8/2014 1:23:52 PM
4480 (0x1180)
NetBIOS_AddName(): LocalName: MP_XXX LanaNumber: 7
SMS_MP_CONTROL_MANAGER 7/8/2014 1:23:52 PM
4480 (0x1180)
RegisterWithWINS: NetBIOS_AddName(LANA=7) returned 0x0
SMS_MP_CONTROL_MANAGER 7/8/2014 1:24:04 PM
4480 (0x1180)
MPStart(): RegisterWithWINS() returned 0x0 SMS_MP_CONTROL_MANAGER
7/8/2014 1:24:04 PM 4480 (0x1180)
MPStart(): PublishInDNS() returned 0x0 SMS_MP_CONTROL_MANAGER
7/8/2014 1:24:04 PM 4480 (0x1180)
Successfully Registered for IP Address Change notifications.
SMS_MP_CONTROL_MANAGER 7/8/2014 1:24:04 PM
4480 (0x1180)
MPStart(): RegisterForIPAddressChangeNotification() returned 0x0
SMS_MP_CONTROL_MANAGER 7/8/2014 1:24:04 PM
4480 (0x1180)
Attempting to register the SQL connection type for the configured SQL database.
SMS_MP_CONTROL_MANAGER 7/8/2014 1:24:04 PM
4480 (0x1180)
Registered connection type for SQL Server 'XXX.com' and database 'SMS_XXX'.
SMS_MP_CONTROL_MANAGER 7/8/2014 1:24:04 PM
4480 (0x1180)
MPStart(): RegisterSqlDatabaseConnectionType() returned 0x0
SMS_MP_CONTROL_MANAGER 7/8/2014 1:24:04 PM
4480 (0x1180)
Checking the current CLR Enabled configuration setting for the configured SQL Server hosting the database.
SMS_MP_CONTROL_MANAGER 7/8/2014 1:24:04 PM
4480 (0x1180)
Getting the CLR Enabled value from the configured SQL database.
SMS_MP_CONTROL_MANAGER 7/8/2014 1:24:04 PM
4480 (0x1180)
Attempting to connect to the configured SQL database.
SMS_MP_CONTROL_MANAGER 7/8/2014 1:24:04 PM
4480 (0x1180)
*** [08001][18][Microsoft][ODBC SQL Server Driver][DBNETLIB]SSL Security error
SMS_MP_CONTROL_MANAGER 7/8/2014 1:29:06 PM
4480 (0x1180)
*** [01000][772][Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (SECDoClientHandshake()).
SMS_MP_CONTROL_MANAGER 7/8/2014 1:29:06 PM
4480 (0x1180)
*** Failed to connect to the SQL Server. SMS_MP_CONTROL_MANAGER
7/8/2014 1:29:06 PM 4480 (0x1180)
Failed to get connection to the configured SQL database.
SMS_MP_CONTROL_MANAGER 7/8/2014 1:29:06 PM
4480 (0x1180)
Failed to connect to the configured SQL database.
SMS_MP_CONTROL_MANAGER 7/8/2014 1:29:06 PM
4480 (0x1180)
Failed to get the current CLR Enabled configuration setting for the configured SQL Server hosting the database.
SMS_MP_CONTROL_MANAGER 7/8/2014 1:29:06 PM
4480 (0x1180)
MPStart(): CheckSqlDatabaseClrEnabled() returned 0x800720d9
SMS_MP_CONTROL_MANAGER 7/8/2014 1:29:06 PM
4480 (0x1180)
Waiting up to 300 seconds for the SMS Agent Host service to be running.
SMS_MP_CONTROL_MANAGER 7/8/2014 1:29:06 PM
4480 (0x1180)
Stopped waiting for the SMS Agent Host service to be running; error = 0x0.
SMS_MP_CONTROL_MANAGER 7/8/2014 1:29:06 PM
4480 (0x1180)
MPStart(): WaitOnSmsAgentHostRunning() returned 0x0
SMS_MP_CONTROL_MANAGER 7/8/2014 1:29:06 PM
4480 (0x1180)
MPStart(): CreateThread() succeeded with id 0xc94.
SMS_MP_CONTROL_MANAGER 7/8/2014 1:29:06 PM
4480 (0x1180)
SMS_MP_CONTROL_MANAGER successfully STARTED.
SMS_MP_CONTROL_MANAGER 7/8/2014 1:29:06 PM
4480 (0x1180)
Configuration and Availability Monitor thread started.
SMS_MP_CONTROL_MANAGER 7/8/2014 1:29:06 PM
3220 (0x0C94)
Initialized 'SMS Server Availability' performance instance => SMS Management Point.
SMS_MP_CONTROL_MANAGER 7/8/2014 1:29:06 PM
3220 (0x0C94)
Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error
Thanks in Advance.
Regards,
Raj.

Yes, I know this is an old post, but I’m trying to clean them up.
Based on your log file the problem appears to be a permission issue. “Failed to connect to the configured SQL database.”
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

CUC 10.0.1 cluster status stuck in Split Brain Recovery (SBR) on Primary server - HA reports fine.

Hi,
Have a 10.01.11900 CUC cluster and everything is working fine (no one having issues with voice mail, etc) but the cluster status reports is not consistent.
DBreplication is showing 2 on both servers.
Primary unity server cluster status shows Primary/split brain recovery.
HA Unity server cluster status shows Primary/Secondary.
utils diagnose test - everything tests fine except the tomcat_connectors test.
test - tomcat_connectors : Failed - The HTTPS port is not responding to local requests. Please collect all of the Tomcat logs for root cause analysis: file get activelog tomcat/logs/*
We've shutdown the HA server and rebooted primary, and then waited awhile after primary was back up/active before bringing the HA server back up and still same.
We reset DB replication and same.
On the HA server I made the HA primary and the cluster status flipped to Seconday/Primary and I then made primary the primary again, but the primary server cluster status always shows Split Brain Recovery for the secondary/HA server.
No core dumps on either server and all services are started.
Any one seen this before or have any thoughts? I have a TAC Case on this but so far in same boat.
Would the utils cuc cluster renegotiate command help? Did not replace a server so don't really want to overwrite data to publisher server. Issue seems to be with the publisher since HA shows fine but not sure. I don't want to lose messages/etc so don't want really want to run these commands.
Thanks.

Ok, thanks.
The SRM logs indicate the Connection Digital Networking Replication Agent service is not running, however when I start it it stops right away and the cuReplicator log states digital networking is not enabled.
From SRM Log:
23:47:20.100 |17755,,,SRM,7,<svcmon> checkServiceStatus: started service monitoring
23:47:20.100 |17755,,,SRM,7,<svcmon> Service Status: 1 service(s) not running. Service name(s):
23:47:20.100 |17755,,,SRM,7,<svcmon> Connection Digital Networking Replication Agent
23:47:24.674 |28471,,,SRM,11,<Timer-3> [snd] Type: Heartbeat
From Replicator log:
admin:file tail activelog cuc/diag_CuReplicator_00000049.uc
23:42:59.208 HDR|09/14/2014 ,Significant
23:42:59.208 |28914,,,CuReplicator,0,Digital Networking is not enabled. Replicator will stop now.
There is no digital networking setup to other unity systems, and only one location.
Also, the Server role manager can't be restarted from CLI or the GUI so either root or a server reboot.
I compared it to another CUC cluster and deactivated the Digital Networking service and the SRM logs seem happier now, will wait a bit and see if it clears the SBR status up.

Sun Ray Server Failover/ Load Sharing

Hi All
I have 2 sun servers which i want to use as sun ray servers in failover/load sharing mode.
I have 60 sun ray thin clients who will access these 2 Sun ray servers.
The users will be using the word, excel and presentation application and save there data in their home directories.
What i want to do is to load share these users between the servers so that any user can connect on anyserver and should be able to see his old data.
Is it a possible configuration?
if yes then please give me idea about how to do it.
I've the system admin document for sun ray server where it says about replication but doesn't tell what data will be replicated between the primary and secondary server.
Can we replicate the the user home accounts and directories as well?
Please assist me.
Thanks in advance..
BR
RAK

I did the all of the following already and it has never work. below is the config for both servers
On the primary
thumper / 502 # utadm -l
LAN connections: Off
Subnetwork: 10.0.1.0
Interface= ce1 (10.0.1.1)
Netmask= 255.255.255.0
Broadcast= 10.0.1.255
Router= 10.0.1.1
AuthSrvr= 10.0.1.1
AltAuth= 10.0.1.1 255.255.255.255
FirmwareSrvr= 10.0.1.1
NewTver= 4.0_48_2007.08.01.15.48
IP assignment= 2/20 (10.0.1.16)
thumper / 501 # utreplica -l
Sun Ray Core Services 4.0
Administration Failover Configuration
thumper.uen.org is a primary server for:
molt.uen.org
On the secondary
molt / 315 # utadm -l
LAN connections: Off
Subnetwork: 10.0.1.0
Interface= ce1 (10.0.1.2)
Netmask= 255.255.255.0
Broadcast= 10.0.1.255
Router= 10.0.1.2
AuthSrvr= 10.0.1.2
AltAuth= 10.0.1.2 255.255.255.255
FirmwareSrvr= 10.0.1.2
NewTver= 4.0_48_2007.08.01.15.48
IP assignment= 7/20 (10.0.1.46)
molt / 314 # utreplica -l
Sun Ray Core Services 4.0
Administration Failover Configuration
molt.uen.org is a secondary server
The primary server is: thumper.uen.org

Agent Primary Server Failover

Similar Messages

Maybe you are looking for