Hi,
I am having multiple issues with my devloper copy of 5.13 on OSX where it works and then suddenly the sybase 11 just wont start anymore.
Last login: Mon Jun 14 17:19:20 on console
/Applications/Servoy5133/application_server/sybase_db/dbsrv11 ; exit;
david-pearces-macbook-air-2:~ dpearce$ /Applications/Servoy5133/application_server/sybase_db/dbsrv11 ; exit;
dyld: Library not loaded: libdbserv11_r.dylib
Referenced from: /Applications/Servoy5133/application_server/sybase_db/dbsrv11
Reason: image not found
Trace/BPT trap
logout
When i try to run sybase directly from the folder i get this response. It seems very random, but being non technical at this level it is annoying to have to reinstall 5.13 to get it working again. It has also happened on both my home mac and my laptop.
Any clues how to get it running again?
David
On closer inspection you cannot double click on this, but it is still odd that on two machines the sybase server just seems to die when started from developer. it doesnt even write to the log file, or come up for a second in the activity monitor.
i tried this from the sybase folder
./dbsrv11 -c 8m @"/Applications/Servoy513Frameworks/application_server/sybase_db/sybase.config"
but that just comes up with Can’t open Message window log file: sybase_db/sybase_log.txt.
Servoy 5.01 still opens sybase fine on the same machines when you open developer. As I say this was working on two machines, then one, then after working on that one last night in developer, i went in this morning and again nothing. Sybase just seems not to open when you start develoer, and the log fiel date is unchanged.
David
dpearce:
On closer inspection you cannot double click on this, but it is still odd that on two machines the sybase server just seems to die when started from developer. it doesnt even write to the log file, or come up for a second in the activity monitor.
i tried this from the sybase folder
./dbsrv11 -c 8m @"/Applications/Servoy513Frameworks/application_server/sybase_db/sybase.config"
but that just comes up with Can’t open Message window log file: sybase_db/sybase_log.txt.
Servoy 5.01 still opens sybase fine on the same machines when you open developer. As I say this was working on two machines, then one, then after working on that one last night in developer, i went in this morning and again nothing. Sybase just seems not to open when you start develoer, and the log fiel date is unchanged.
David
You must run the command from application_server folder (as current folder) because we use relative paths. So something like: ./dbsrv11 -c 8m @“/sybase_db/sybase.config” . Do you have the libdbserv11_r.dylib file in sybase_db folder ?
Yes the file is definitely in the sybase_db folder.
This worked fine from the intial servoy install and then just stopped working. The same has happened spontaneously on my other mac.
from the application_server directory i just tried:
david-pearces-macbook-air-2:application_server dpearce$ ./sybase_db/dbsrv11 -c 8m @"sybase_db/sybase.config"
dyld: Library not loaded: libdbserv11_r.dylib
Referenced from: /Applications/Servoy5133/application_server/./sybase_db/dbsrv11
Reason: image not found
Trace/BPT trap
david-pearces-macbook-air-2:application_server dpearce$
The file is definitely there, but as you can see, this worked until I quit sybase yesterday morning as i was running servoy 3.5 on the same machine, and then hasnt started since. I have made sure sybase 10 is not running. The odd thing is that my install of 5.01 is unaffected, and has not failed, it just seems on 5.13 that this is happening on multiple machines.
You must also specify some paths to manually start on mac, see for example, viewtopic.php?f=5&t=13845
Yes that worked!
LC_CTYPE=C LANG=C DYLD_LIBRARY_PATH=sybase_db sybase_db/dbspawn sybase_db/dbsrv11 @sybase_db/sybase.config
its strange that the Developer changes so not to start sybase in 5.13 when it never and still doesn’t in 5.01, maybe it is related to me using 3.5, that when i stop DBSERV11 and use 10 for 3.5 that when it starts again it has changed a path or something.
Anyway, this is a workaround for now!
Thanks
David
