The forum will be down for scheduled maintenance on Saturday, March 4 beginning at 10am EST. Actual downtime is unknown but may be several hours.

What are the conditions under which a storm of "AcceptConn: DB not found" messages appear in the 12.0.1.3298 arbiter server console log?

FWIW searching the V16 Help for AcceptConn yields no hits, and a Google search is similarly fruitless.

I. 03/09 18:05:12. SQL Anywhere Network Server Version 12.0.1.3298

I. 03/09 18:05:12. Developer edition, not licensed for deployment.
I. 03/09 18:05:12.

I. 03/09 18:05:12. Copyright © 2001-2011, iAnywhere Solutions, Inc.
I. 03/09 18:05:12. Portions copyright © 1988-2011, Sybase, Inc. All rights reserved.
I. 03/09 18:05:12. Use of this software is governed by the Sybase License Agreement.
I. 03/09 18:05:12. Refer to http://www.sybase.com/softwarelicenses.
I. 03/09 18:05:12.

I. 03/09 18:05:12. Connection limit (licensed seats): 3
I. 03/09 18:05:12. Processors detected: 1 (containing 8 logical processors)
I. 03/09 18:05:12. Maximum number of physical processors the server will use: 1
I. 03/09 18:05:12. This server is licensed to:
I. 03/09 18:05:12.     Breck
I. 03/09 18:05:12.     Hewlett-Packard
I. 03/09 18:05:12. Running Windows 7 Build 7601 Service Pack 1 on X86_64
I. 03/09 18:05:12. Server built for X86 processor architecture
I. 03/09 18:05:12. 3576K of memory used for caching
I. 03/09 18:05:12. Minimum cache size: 2956K, maximum cache size: 3482728K
I. 03/09 18:05:12. Using a maximum page size of 4096 bytes
I. 03/09 18:05:12. Multiprogramming level: minimum:8, current:20, maximum:80
I. 03/09 18:05:12. Automatic tuning of multiprogramming level is enabled
I. 03/09 18:05:12. Starting database "arbiter_demo" (C:\$ blogs and websites\blog SQLAnywhere\20140311 PENDING Giving The Arbiter A Database\demo declarative revision 1\arbiter\arbiter_demo.db) at Sun Mar 09 2014 18:05
I. 03/09 18:05:12. Performance warning: Database file "C:\$ blogs and websites\blog SQLAnywhere\20140311 PENDING Giving The Arbiter A Database\demo declarative revision 1\arbiter\arbiter_demo.db" consists of 19 disk fragments
I. 03/09 18:05:12. Transaction log: arbiter_demo.log
I. 03/09 18:05:12. Starting checkpoint of "arbiter_demo" (arbiter_demo.db) at Sun Mar 09 2014 18:05
I. 03/09 18:05:12. Finished checkpoint of "arbiter_demo" (arbiter_demo.db) at Sun Mar 09 2014 18:05
I. 03/09 18:05:13. Database "arbiter_demo" (arbiter_demo.db) started at Sun Mar 09 2014 18:05
I. 03/09 18:05:13. Database server started at Sun Mar 09 2014 18:05
I. 03/09 18:05:13. Trying to start SharedMemory link ...
I. 03/09 18:05:13.     SharedMemory link started successfully
I. 03/09 18:05:13. Trying to start TCPIP link ...
I. 03/09 18:05:13. Starting on port 55400
I. 03/09 18:05:13.     TCPIP link started successfully
I. 03/09 18:05:13. Now accepting requests
E. 03/09 18:05:13. AcceptConn: DB not found
E. 03/09 18:05:13. AcceptConn: DB not found
E. 03/09 18:05:17. AcceptConn: DB not found
E. 03/09 18:05:17. AcceptConn: DB not found
E. 03/09 18:05:20. AcceptConn: DB not found
E. 03/09 18:05:20. AcceptConn: DB not found
E. 03/09 18:05:23. AcceptConn: DB not found
E. 03/09 18:05:24. AcceptConn: DB not found
E. 03/09 18:05:27. AcceptConn: DB not found
E. 03/09 18:05:27. AcceptConn: DB not found
E. 03/09 18:05:30. AcceptConn: DB not found
E. 03/09 18:05:31. AcceptConn: DB not found
E. 03/09 18:05:34. AcceptConn: DB not found
E. 03/09 18:05:34. AcceptConn: DB not found
E. 03/09 18:05:37. AcceptConn: DB not found
E. 03/09 18:05:38. AcceptConn: DB not found
E. 03/09 18:05:41. AcceptConn: DB not found
E. 03/09 18:05:41. AcceptConn: DB not found
E. 03/09 18:05:44. AcceptConn: DB not found
E. 03/09 18:05:44. AcceptConn: DB not found
E. 03/09 18:05:48. AcceptConn: DB not found
E. 03/09 18:05:48. AcceptConn: DB not found
E. 03/09 18:05:51. AcceptConn: DB not found
E. 03/09 18:05:51. AcceptConn: DB not found
E. 03/09 18:05:55. AcceptConn: DB not found
E. 03/09 18:05:55. AcceptConn: DB not found
E. 03/09 18:05:58. AcceptConn: DB not found
E. 03/09 18:05:58. AcceptConn: DB not found
E. 03/09 18:06:02. AcceptConn: DB not found
E. 03/09 18:06:02. AcceptConn: DB not found
E. 03/09 18:06:05. AcceptConn: DB not found
E. 03/09 18:06:05. AcceptConn: DB not found
E. 03/09 18:06:09. AcceptConn: DB not found
E. 03/09 18:06:09. AcceptConn: DB not found
E. 03/09 18:06:12. AcceptConn: DB not found
E. 03/09 18:06:12. AcceptConn: DB not found
E. 03/09 18:06:16. AcceptConn: DB not found
E. 03/09 18:06:16. AcceptConn: DB not found
I. 03/09 18:06:19. Cache size adjusted to 4540K
E. 03/09 18:06:19. AcceptConn: DB not found
E. 03/09 18:06:19. AcceptConn: DB not found
E. 03/09 18:06:23. AcceptConn: DB not found
E. 03/09 18:06:23. AcceptConn: DB not found
E. 03/09 18:06:26. AcceptConn: DB not found
E. 03/09 18:06:26. AcceptConn: DB not found
I. 03/09 18:06:29. Cache size adjusted to 4884K
E. 03/09 18:06:30. AcceptConn: DB not found
E. 03/09 18:06:30. AcceptConn: DB not found
E. 03/09 18:06:33. AcceptConn: DB not found
E. 03/09 18:06:33. AcceptConn: DB not found
E. 03/09 18:06:37. AcceptConn: DB not found
E. 03/09 18:06:37. AcceptConn: DB not found
E. 03/09 18:06:40. AcceptConn: DB not found
E. 03/09 18:06:40. AcceptConn: DB not found
E. 03/09 18:06:44. AcceptConn: DB not found
E. 03/09 18:06:44. AcceptConn: DB not found
E. 03/09 18:06:47. AcceptConn: DB not found
E. 03/09 18:06:47. AcceptConn: DB not found
E. 03/09 18:06:51. AcceptConn: DB not found
E. 03/09 18:06:51. AcceptConn: DB not found
E. 03/09 18:06:54. AcceptConn: DB not found
E. 03/09 18:06:54. AcceptConn: DB not found
E. 03/09 18:06:58. AcceptConn: DB not found
E. 03/09 18:06:58. AcceptConn: DB not found
E. 03/09 18:07:01. AcceptConn: DB not found
E. 03/09 18:07:01. AcceptConn: DB not found
E. 03/09 18:07:05. AcceptConn: DB not found
E. 03/09 18:07:05. AcceptConn: DB not found
E. 03/09 18:07:08. AcceptConn: DB not found
E. 03/09 18:07:08. AcceptConn: DB not found
E. 03/09 18:07:12. AcceptConn: DB not found
E. 03/09 18:07:12. AcceptConn: DB not found
E. 03/09 18:07:15. AcceptConn: DB not found
E. 03/09 18:07:15. AcceptConn: DB not found
E. 03/09 18:07:19. AcceptConn: DB not found
E. 03/09 18:07:19. AcceptConn: DB not found
E. 03/09 18:07:22. AcceptConn: DB not found
E. 03/09 18:07:22. AcceptConn: DB not found
E. 03/09 18:07:26. AcceptConn: DB not found
E. 03/09 18:07:26. AcceptConn: DB not found
E. 03/09 18:07:29. AcceptConn: DB not found
E. 03/09 18:07:29. AcceptConn: DB not found
E. 03/09 18:07:31. AcceptConn: DB not found
E. 03/09 18:07:44. AcceptConn: DB not found
E. 03/09 18:07:48. AcceptConn: DB not found
E. 03/09 18:07:55. AcceptConn: DB not found
E. 03/09 18:07:58. AcceptConn: DB not found
E. 03/09 18:08:02. AcceptConn: DB not found
E. 03/09 18:08:06. AcceptConn: DB not found
E. 03/09 18:08:10. AcceptConn: DB not found
E. 03/09 18:08:14. AcceptConn: DB not found
E. 03/09 18:08:18. AcceptConn: DB not found
E. 03/09 18:08:21. AcceptConn: DB not found
E. 03/09 18:08:25. AcceptConn: DB not found
E. 03/09 18:08:29. AcceptConn: DB not found
E. 03/09 18:08:33. AcceptConn: DB not found
E. 03/09 18:08:37. AcceptConn: DB not found
E. 03/09 18:08:41. AcceptConn: DB not found
E. 03/09 18:08:44. AcceptConn: DB not found
E. 03/09 18:08:48. AcceptConn: DB not found
E. 03/09 18:08:52. AcceptConn: DB not found
E. 03/09 18:08:56. AcceptConn: DB not found
E. 03/09 18:09:00. AcceptConn: DB not found
E. 03/09 18:09:04. AcceptConn: DB not found
E. 03/09 18:09:08. AcceptConn: DB not found
E. 03/09 18:09:12. AcceptConn: DB not found
E. 03/09 18:09:16. AcceptConn: DB not found
E. 03/09 18:09:20. AcceptConn: DB not found
E. 03/09 18:09:24. AcceptConn: DB not found
E. 03/09 18:09:27. AcceptConn: DB not found
E. 03/09 18:09:31. AcceptConn: DB not found
E. 03/09 18:09:35. AcceptConn: DB not found
E. 03/09 18:09:39. AcceptConn: DB not found
E. 03/09 18:09:43. AcceptConn: DB not found
E. 03/09 18:09:46. AcceptConn: DB not found
E. 03/09 18:09:50. AcceptConn: DB not found
E. 03/09 18:09:54. AcceptConn: DB not found
E. 03/09 18:09:59. AcceptConn: DB not found
E. 03/09 18:10:03. AcceptConn: DB not found
E. 03/09 18:10:07. AcceptConn: DB not found
E. 03/09 18:10:10. AcceptConn: DB not found
E. 03/09 18:10:14. AcceptConn: DB not found
E. 03/09 18:10:18. AcceptConn: DB not found
E. 03/09 18:10:22. AcceptConn: DB not found
E. 03/09 18:10:26. AcceptConn: DB not found
E. 03/09 18:10:30. AcceptConn: DB not found
E. 03/09 18:10:33. AcceptConn: DB not found
E. 03/09 18:10:37. AcceptConn: DB not found
E. 03/09 18:10:42. AcceptConn: DB not found
E. 03/09 18:10:46. AcceptConn: DB not found
E. 03/09 18:10:50. AcceptConn: DB not found
E. 03/09 18:10:53. AcceptConn: DB not found
E. 03/09 18:10:57. AcceptConn: DB not found
E. 03/09 18:11:01. AcceptConn: DB not found
E. 03/09 18:11:04. AcceptConn: DB not found
E. 03/09 18:11:07. AcceptConn: DB not found
E. 03/09 18:11:11. AcceptConn: DB not found
E. 03/09 18:11:13. AcceptConn: DB not found
E. 03/09 18:11:13. AcceptConn: DB not found
E. 03/09 18:11:14. AcceptConn: DB not found
E. 03/09 18:11:14. AcceptConn: DB not found
E. 03/09 18:11:15. AcceptConn: DB not found
E. 03/09 18:11:16. AcceptConn: DB not found
E. 03/09 18:11:18. AcceptConn: DB not found
E. 03/09 18:11:19. AcceptConn: DB not found
E. 03/09 18:11:21. AcceptConn: DB not found
E. 03/09 18:11:22. AcceptConn: DB not found
E. 03/09 18:11:25. AcceptConn: DB not found
E. 03/09 18:11:26. AcceptConn: DB not found
E. 03/09 18:11:28. AcceptConn: DB not found
E. 03/09 18:11:29. AcceptConn: DB not found
I. 03/09 18:11:29. Database server shutdown requested via server console
W. 03/09 18:11:29. TCPIP listener on IP address (::):55400 is exiting
W. 03/09 18:11:29. TCPIP listener on IP address 0.0.0.0:55400 is exiting
I. 03/09 18:11:29. Starting checkpoint of "arbiter_demo" (arbiter_demo.db) at Sun Mar 09 2014 18:11
I. 03/09 18:11:30. Finished checkpoint of "arbiter_demo" (arbiter_demo.db) at Sun Mar 09 2014 18:11
I. 03/09 18:11:30. Database server stopped at Sun Mar 09 2014 18:11

asked 09 Mar '14, 18:16

Breck%20Carter's gravatar image

Breck Carter
26.8k421580826
accept rate: 20%

edited 09 Mar '14, 18:19

Are you specifying a database name using the -xa switch? Does it match the database name used on the primary and mirror? This error can occur is the database names do not match.

(09 Mar '14, 19:58) Mikel Rychliski
Replies hidden

Yes, that is one way to get that error. Is it the only way? Why does it cause a storm of messages? Why is it not documented?

(09 Mar '14, 21:17) Breck Carter

In 12.0.1.3298, this message may be printed any time a mirroring server tries to connect to another mirroring server, but the destination server is not configured to run with the expected database. As Mikel pointed out, on an arbiter this message is most likely generated when the arbiter server is being requested by another server (primary, mirror) to be the arbiter for a database, but the server is not configured to be the arbiter of that database. I believe something similar could happen between any permutation of primary and mirror servers if they aren't running the same database as well.

A message is generated every time a server tries to connect, explaining the storm of messages.

For the sake of completeness, if someone tried to connect using diagnostics to a database on server, where the database is not running on that server, this message would also be possible.

Note that in versions 12.0.1.3391+, the message "AcceptConn: DB not found" was completely removed from the mirroring case. For the arbiter scenario, I would expect a more helpful message to be printed: "Not an arbiter for database <dbname>".

The message was not explicitly documented because it wasn't created in the standard way for output to users - it might have even been intended as debug information. Regardless, it's been replaced by now. I'm not sure the behaviour is explicitly documented, but I don't think it's unreasonable to extrapolate from the documentation that if the arbiter isn't configured for a database, it's not going to accept connections to it.

permanent link

answered 10 Mar '14, 15:51

MarySteele's gravatar image

MarySteele
23124
accept rate: 66%

edited 10 Mar '14, 15:52

@Breck: So you may feel to leave that "golden 12.0.1 EBF 3298" behind you, don't you think?

(11 Mar '14, 04:46) Volker Barth
Replies hidden

Yeah... it's the version mentioned in the Foxhound 2 Requirements so periodically I reinstall it to check something Foxhound-related... then I forget to upgrade back to something [cough] less ancient.

But... I have clients doing new development with Version 9.0.2 which kinda puts my life in perspective :)

(11 Mar '14, 11:57) Breck Carter

Well, we still use a (third-party) application running with v5.5.05.2817 - that will make you feel even better:)

(11 Mar '14, 12:37) Volker Barth
Comment Text Removed

Wow, do you have the db*.exe binaries for that? I have 5.5.5.2787, and I doubt that an old-style patch would work even if I could find one. Just because folks don't do much new development doesn't mean they don't do maintenance, so I try to keep the cellar fully stocked :)

(11 Mar '14, 15:04) Breck Carter

Well, I will see what I can do - guess I have your e-mail address:)

(12 Mar '14, 04:51) Volker Barth
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×101

question asked: 09 Mar '14, 18:16

question was seen: 2,946 times

last updated: 12 Mar '14, 04:51