Unstable Mar work
I started to research Mar development, and one moment is not clear for me.
When I deploy the same code of my project to Mar git server, it starts correctly from time to time.
For example, the first half of day Mar console shows
Process <processId> received event: start Process <processId> received event: die <PATH_TO_BIN>: error while loading shared libraries: lib*.so.1: cannot open shared object file: No such file or directory.
Several times there were messages about tar archive error.
Another part of day everything is OK.
Does it mean that Mar work is unstable now ? May be there is any updating processes of Mar infrastructure or simple any bug? And what should I do in this case?
Thanks a lot.
Mar should be pretty stable at this point. Usually problems start to rise when application is hitting instance memory limits or the compiled app (slug) size is too big (> 150MB). Mar is reporting slug size at the end of git push output.
@jakolehm May be this dependent from location, but here, from Saint-Petersburg the Mar work from time to time.
I don't can describe all problems because I don't can to localize these bugs by in many reasones.
But this is a fact that QMAKE_ARGS not work, or work not always, the succesfully compiled MAR application sometimes can not be started, but can be started from my computer or in another time on MAR.
With running MAR application I don't have problems, but exist problems with deploying,
I hope, that all of these problems I will resolve or localize when I will have remote access to MAR via ssh.
@jakolehm As I noticed new Ubuntu hosts have appeared for Mar. But when I run my application with websockets on this new platform and connect to MDB instance, I get
QSqlDatabase: QMYSQL driver not loaded QSqlDatabase: available drivers: QSQLITE QMYSQL QMYSQL3 QPSQL QPSQL7 "Driver not loaded Driver not loaded"
Is it mean that database driver for sql wasn't installed now on new platform yet ?
On Ubuntu 10.04 everything is ok.
The same problem with new Ubuntu host.
Good catch, I added an issue about this to our Qt buildpack repo: https://github.com/qtcloudservices/qtc-buildpack-qt/issues/2
Possible workaround for this problem (while we investigate how to fix this):
BUILDPACK_URL=https://github.com/ddollar/heroku-buildpack-multi.gitenvironment variable (through console or qtc-cli)
.buildpacksfile to root of your project with following contents:
Debfileto root of your project with following contents:
- git push update to MAR
We have built Qt 5.5beta snapshot for Ubuntu 14.04 stack. You can test it by setting
.qt_runtimefile on project root.
Edit: it seems that this does not fix mysql problems :(
Now there is totally new build available for Ubuntu 14.04 (built from scratch). You can test it by setting
.qt_runtimefile in your project root folder. @kolisergej , @Milovidov please test and report if this fixes mysql problems.
@jakolehm I have created hidden .qt_runtime file and fill it as you wrote. But my try wasn't successful.
When I deployed code for compiling on your server I caught following:
remote: [1G Project ERROR: Unknown module(s) in QT: script remote: [1G make: *** <<Project Name>> Error 3[K remote: [1G ERROR: build failed to complete[K
@kolisergej , this Qt build was missing a qtscript module. It's now included so please test again :)
Btw: used Qt build parameters can be seen from here: https://github.com/qtcloudservices/qtc-buildpack-qt/blob/master/package_qt.sh#L18
@jakolehm Yes now everything works good. we did it)
By the way, as I noticed with new platform slug size have become much less (in 2.5 times).
And also earlier I had some problems with dynamic libraries, an had to to specify
CONFIG += staticlib
when deployed code in .pro file and in QMAKE_ARGS in environment. Now everything works without this, and I haven't problems with dynamic libraries. Thank you for your work.
@jakolehm hello once more.
Unfortunately Mar work is unstable again now (
When I push code to your remote host, I get.
Process web:8dda4ae5742d received event: start ./Build/Release/<<My binary file>>: error while loading shared libraries: lib<<my lib name>>.so.1: cannot open shared object file: No such file or directory
Some days ago everything was alright
@jakolehm It's very strange. Now everything is ok.
From time to time I have problems with shared libs as above.
Could you say please what may be wrong?
@jakolehm And no I caught the same fail again
Sorry, I don't know what could cause that kind of instability. Build/compile phase uses always fresh environment so it should behave always the same way. If you have the possibility to install docker on your machine then it might be easier to debug because you could run that build/compile phase on your computer.