I'm trying to run the community installation within docker with this process:
https://github.com/ant-media/Ant-Media-Server/wiki/Building-and-Running-Docker-Container-for-Ant-Media-Server
And at the end of the build i'm getting
Errors were encountered while processing:
/var/cache/apt/archives/libllvm6.0_1%3a6.0-1ubuntu2~16.04.1_amd64.deb
/var/cache/apt/archives/openjdk-8-jdk-headless_8u265-b01-0ubuntu2~16.04_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Get a diffrent error in the build process of Enterprise edition , changing the ubuntu version to 18 finally completes the installation but it seems that the server is not starting.
Am i missing something obvious ?
Related
I installed Wordpress Packaged by Bitnami and made a website on it. It was working fine the whole month but now the website stopped working and when access any of the following
http://localhost/wordpress/
http://localhost/wordpress/wp-admin
http://localhost/wordpress/phpmyadmin
I get the following error "Error establishing a database connection"
Manger Tool > Manage Servers shows MariaDB Database Stopped, Apache Web Server Running
When try to Start MariaDB it doesn't start and I get the following:
Manger Tool > Server Events
Starting MariaDB Database... Exit code: 1 Stdout:
Stderr: Unknown error starting mysql
What's the cause and solution?
mysqld
I would recommend you to check the mysqld log file regarding the errors you have, which are triggering it to not to run.
which is in /bitnami/wordpress-5.8.1-2/mariadb/data/mysqld.log
in this file you will find detailed information about the error.
UPDATE
After attaching the log file, I discovered that this issue is similar to this one How to fix Error: MySQL shutdown unexpectedly on Xampp due to Plugin 'Aria', and solution might be applied following the steps:
Remove aria_log_control file from /bitnami/wordpress-5.8.1-2/mariadb/data/
Start the service
I am running a windows server with MySQL I installed together with XAMPP - MySQL Ver 15.1 Distrib 10.4.11-MariaDB, for Win64 (AMD64), source revision 7c2c420b70b19cc02b5281127205e876f3919dad
When I run sqitch deploy I keep getting error - "mysql.exe" unexpectedly returned exit value 1 and a lot of other version information about MySQL in screenshot below:
What can I do to resolve error please?
I have been successfully running a build definition against a dotnet core web application for months now but the build has started to fail. The error occurs when trying to run a dotnet restore command on my projects.
https://i.imgur.com/4EioYjr.png
I am getting the following error when the restore task runs:
Retrying 'FindPackagesByIdAsync' for source 'https://api.nuget.org/v3-
flatcontainer/netcore.mailkit/index.json'.
Response status code does not indicate success: 504 (Gateway Timeout).
Retrying 'FindPackagesByIdAsync' for source 'https://api.nuget.org/v3-
flatcontainer/netcore.mailkit/index.json'.
Response status code does not indicate success: 504 (Gateway Timeout).
I have manually run the dotnet restore command on my local machine and do not get the error.
Has anyone experienced something like this before in VSTS?
Thanks
This looks like it was a Microsoft issue.
http://blogs.msdn.microsoft.com/vsoservice/?p=15195
https://developercommunity.visualstudio.com/content/problem/129183/getting-504-gateway-timeout-on-hosted-vs2017-agent.html
I'm trying to start a new mean stack application. However i only get this error when I'm running grunt to start the server:
[nodemon] v1.2.1
Running "watch" task
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: *.*
[nodemon] starting `node --debug server.js`
Waiting...
Debugger listening on port 5858
Mean app started on port 3000 (development) cluster.worker.id: 0
/Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/connection/base.js:246
throw message;
^
TypeError: Cannot read property 'length' of undefined
at processResults (/Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/db.js:1581:31)
at /Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/db.js:1619:20
at /Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/db.js:1157:7
at /Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/db.js:1890:9
at Server.Base._callHandler (/Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/connection/base.js:448:41)
at /Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/connection/server.js:481:18
at MongoReply.parseBody (/Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/responses/mongo_reply.js:68:5)
at null.<anonymous> (/Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/connection/server.js:439:20)
at emit (events.js:107:17)
at null.<anonymous> (/Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:201:13)
[nodemon] app crashed - waiting for file changes before starting...
Have any one encountered this before? Can't find too many other people who have encountered this before.
I was also facing the same error and this info solves it.
"Upgrade to 3.8.23. 3.8.22 introduced better compatibility with mongodb server 3.0 by upgrading to latest version of the driver." credit to vkarpov15 from mongoose Github thread.
What I did was I edit my package.json to upgrade mongoose to "3.8.23". After I edited the package.json I ran npm install and bower install(just to make sure) again and that solved the problem.
Fresh install of Meteor 0.5.0 on Windows Vista. I don't get the basic examples working. No success after creating the empty'ish hello app either. The shell is running as admin. Meteor recognises that I changed a source file, but then nothing. It doesn't matter where in the filesystem i try this. Always getting
Exited with code: -1073741819:
eg
C:\Users\jawford\Meteor Apps\Examples>meteor create starter3
starter3: created.
To run your new app:
cd starter3
meteor
C:\Users\jawford\Meteor Apps\Examples>cd starter3
C:\Users\jawford\Meteor Apps\Examples\starter3>meteor
[[[[[ C:\Users\jawford\Meteor Apps\Examples\starter3 ]]]]]
Running on: http://localhost:3000/
Exited with code: -1073741819
Exited with code: -1073741819
Exited with code: -1073741819
Your application is crashing. Waiting for file change.
=> Modified -- restarting.
Exited with code: -1073741819
Exited with code: -1073741819
Exited with code: -1073741819
Your application is crashing. Waiting for file change.
^CTerminate batch job (Y/N)? y
C:\Users\jawford\Meteor Apps\Examples\starter3>
If you run into this problem using Windows 8, you will need to change compatibility mode for the node executable.
Go to the folder where you installed Meteor
Open properties for bin/node.exe
Set compatibility mode for Windows 7
You should now be able to start the application as you did earlier.
This has to do with Fibers not loading correctly. You can attempt to run app/meteor/meteor.js with bin/node, both are in the Meteor directory in Program Files. This could maybe give you more details why it is crashing. It might also be handy to run the tests in the lib/node_modules/fibers folder which might point out why Fibers is misbehaving.
The exit code -1073741819 corresponds to C0000005 which indicates an access violation.
Many users find that setting compatibility mode to "Windows 7" solves that problem, but it doesn't always and there is some evidence that it also occurs on Windows 7.
Investigating a later issue on win Meteor 0.5.9, I discovered a problem with fibers on windows that may explain this issue, and I have a tentative fix.
Please see: https://github.com/TomWij/meteor/issues/66#issuecomment-15994548 for further details.