Server 5.0.3 Profile Manager - A server error has occurred after upgrade

betolley's picture

betolley

Joined: Sep 12, 2016
Your rating: None (1 vote)

I upgraded to Server 5.0.3 yesterday. I previously was unable to sync new VPP purchased apps(Last couple weeks) and apple support said I had to updated before VPP would work again. So I upgraded. I am able to login and the apps are there. But randomly I get grey screen or "A server error has occurred." while working. Usually I get one of those errors instead of the page or button I click. I have monitored the log files after hitting load until I get the error: The server starts running version slow at this time. It is a i7 with 16gb of ram. Any suggestions? Any help appreciated.

devicemgrd.log
Nothing

(log follows below)

profilemanager.loga
[379] [2015/09/18 21:52:15.959] I: >>>do_magic: UserGroupHelper.get_complete_details({"ids"=>[8086]})
[382] [2015/09/18 21:52:27.831] I: @@@ Retry #5 of 'MagicController#do_magic' due to database transaction conflict.... (in 0.01953404445505121us)@@@
[382] [2015/09/18 21:52:27.854] I: >>>do_magic: UserGroupHelper.get_complete_details({"ids"=>[8086]})
[377] [2015/09/18 21:52:40.164] I: @@@ Retry #5 of 'MagicController#do_magic' due to database transaction conflict.... (in 0.0038508449925701593us)@@@

In the PostgreSql log file I see:
5-09-18 21:54:07.287 EDT LOG: process 501 still waiting for ExclusiveLock on relation 18254 of database 16384 after 1000.092 ms
2015-09-18 21:54:07.287 EDT CONTEXT: SQL statement "LOCK TABLE library_items_assets IN EXCLUSIVE MODE"
PL/pgSQL function dm_app_info_for_user_group(integer) line 9 at SQL statement
2015-09-18 21:54:07.287 EDT STATEMENT: SELECT dm_app_info_for_user_group(5512)
2015-09-18 21:54:17.813 EDT ERROR: could not serialize access due to read/write dependencies among transactions
2015-09-18 21:54:17.813 EDT DETAIL: Reason code: Canceled on identification as a pivot, during write.
2015-09-18 21:54:17.813 EDT HINT: The transaction might succeed if retried.
2015-09-18 21:54:17.813 EDT CONTEXT: SQL statement "INSERT INTO db_notifications (channel,message) VALUES ('objc_send', the_message)"
PL/pgSQL function _dm_objc_send(character varying) line 7 at SQL statement
SQL statement "SELECT _dm_objc_send(TG_ARGV[0]::varchar)"
PL/pgSQL function dm_trigger_objc_send() line 6 at PERFORM
2015-09-18 21:54:17.813 EDT STATEMENT: INSERT INTO od_searches
(search_type,match_type,attribute,query_value)
VALUES
(2,8193,'dsAttrTypeStandard:GeneratedUID','c815c36c-8366-44b8-b180-41615e03ae07 ')

2015-09-18 21:54:17.813 EDT LOG: process 497 acquired ExclusiveLock on relation 18254 of database 16384 after 60644.826 ms
2015-09-18 21:54:17.813 EDT CONTEXT: SQL statement "LOCK TABLE library_items_assets IN EXCLUSIVE MODE"
PL/pgSQL function dm_app_info_for_user_group(integer) line 9 at SQL statement
2015-09-18 21:54:17.813 EDT STATEMENT: SELECT dm_app_info_for_user_group(7988)
2015-09-18 21:54:19.056 EDT LOG: process 499 still waiting for ExclusiveLock on relation 18254 of database 16384 after 1001.017 ms
2015-09-18 21:54:19.056 EDT CONTEXT: SQL statement "LOCK TABLE library_items_assets IN EXCLUSIVE MODE"
PL/pgSQL function dm_app_info_for_user_group(integer) line 9 at SQL statement
2015-09-18 21:54:19.056 EDT STATEMENT: SELECT dm_app_info_for_user_group(5512)
2015-09-18 21:54:29.766 EDT ERROR: could not serialize access due to read/write dependencies among transactions
2015-09-18 21:54:29.766 EDT DETAIL: Reason code: Canceled on identification as a pivot, during write.
2015-09-18 21:54:29.766 EDT HINT: The transaction might succeed if retried.
2015-09-18 21:54:29.766 EDT CONTEXT: SQL statement "INSERT INTO db_notifications (channel,message) VALUES ('objc_send', the_message)"
PL/pgSQL function _dm_objc_send(character varying) line 7 at SQL statement
SQL statement "SELECT _dm_objc_send(TG_ARGV[0]::varchar)"
PL/pgSQL function dm_trigger_objc_send() line 6 at PERFORM
2015-09-18 21:54:29.766 EDT STATEMENT: INSERT INTO od_searches
(search_type,match_type,attribute,query_value)
VALUES
(2,8193,'dsAttrTypeStandard:GeneratedUID','a3c9ac34-9c4a-40a3-929e-ad5461ba892e ')

2015-09-18 21:54:29.766 EDT LOG: process 498 acquired ExclusiveLock on relation 18254 of database 16384 after 59182.600 ms
2015-09-18 21:54:29.766 EDT CONTEXT: SQL statement "LOCK TABLE library_items_assets IN EXCLUSIVE MODE"
PL/pgSQL function dm_app_info_for_user_group(integer) line 9 at SQL statement
2015-09-18 21:54:29.766 EDT STATEMENT: SELECT dm_app_info_for_user_group(8086)
2015-09-18 21:54:31.176 EDT LOG: process 497 still waiting for ExclusiveLock on relation 18254 of database 16384 after 1000.609 ms
2015-09-18 21:54:31.176 EDT CONTEXT: SQL statement "LOCK TABLE library_items_assets IN EXCLUSIVE MODE"
PL/pgSQL function dm_app_info_for_user_group(integer) line 9 at SQL statement
2015-09-18 21:54:31.176 EDT STATEMENT: SELECT dm_app_info_for_user_group(7988)

Mac mini, OS X Yosemite (10.10.5)
I have this question too Show 2 Likes (2)

Top
betolley's picture

betolley

Joined: Oct 16, 2014

Have been told by Apple

Your rating: None

Have been told by Apple Support that upgrading from previous version to Server 5.0.3 causes time out problems and they are aware.

Top
kbazzor's picture

kbazzor

Joined: Dec 21, 2015

Anyone get a solution to this?

Your rating: None

Its a huge problem and is still occurring on my server close to 5 months later

Ive contacted apple enterprise support and they just shrugged me off said its a known issue and that's all, no eta on the fix, no mention of a patch...looks a little like the update may have caused irreversible damage to the database or something very suspicious.

Thanks for any info that may help

Top

Who is online?

There are currently 0 admins, 0 users and 34 guests online. Connected users: .

Recent Activity