We are using JDBC Connection in airflow to fetch data from a public MySQL server. The connection was setup fine and worked as expected in the local machine but I received the following error in composer.
[Errno 2] No such file or directory: '/usr/lib/jvm'
I m currently thinking if
Am I doing something wrong ?
JVM is unavailable in Composer webserver?
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
Im trying to upload a conan package to a remote Artifactory server. I want revisions to be disabled so I use CONAN_REVISIONS_ENABLED=0. However I get the following error:
ERROR: 404 Client Error: Not Found for url: https://<SERVER>/artifactory/api/conan/<SERVER_ALIAS>/v1/files/<PACKAGE>/0/export/conanfile.py
If I set CONAN_REVISIONS_ENABLED=1 the upload works fine. The server is configured for local repositorys (virtual or remote repos does not exists) so the APIv1 should work.
Is there a configuration on the server side that I have missed that might cause this error?
Artifactory version is: 6.13.1
Repository layout is: conan-default
For the background to this question see this issue on github.
After downloading Realm browser, i tried to connect it with our linux server where Realm Object Server is installed (professional edition).
Initially it was showing Timeout error constantly after that i tried to run Realm Studio as administrator and it started working.
I was trying run EventBlank example provided by realm
i was able to create database and users too over realm and can see it on realm studio but after a while when i tried to reopen realm studio and connect with the same realm object server url it is throwing unknown error
here is the server log while unknown error occured
Timeout error
Following things i have tried
1) re install realm studio
2) while installing run it as admin
3) turning off the firewall on windows
but it still throwing unknown error and timeout error
I am running realm object server using
ros start --address <ipaddress> --port <port>
server start log
After inspecting , this is what i got ( i have updated realm studio to 1.4 )
I have a cloud service on Windows Azure, I created a Asp.net WebAPI project and published to the cloud service, that was working fine from Visual Studio to publish before i updated visual studio to update 4 and azure SDK 2.2 to 2.6. But after updating when I publish, I got the following error messages. I tried several times, all failed. Can anyone help me?
even i am not able to publish a new created project on new azure service !
11:00:31 PM - Warning: There are package validation warnings.
11:00:31 PM - Checking for Remote Desktop certificate...
11:00:39 PM - Preparing deployment for TempAzure - 2/12/2014 10:58:23
PM with Subscription ID 'e94e9aeb-7003-4eae-be92-7b7ac0a1ba2c' using
Service Management URL 'https://management.core.windows.net/'...
11:00:39 PM - Connecting...
11:00:39 PM - Verifying storage account 'jasontest'...
11:00:41 PM - Uploading Package...
11:06:48 PM - Warning: The remote server returned an error: (500)
Internal Server Error.
11:11:50 PM - Warning: The remote server returned an error: (500)
Internal Server Error.
11:26:16 PM - Warning: The remote server returned an error: (500)
Internal Server Error.
12:00:27 AM - Warning: The remote server returned an error: (500)
Internal Server Error.
12:05:05 AM - Warning: The remote server returned an error: (500)
Internal Server Error.
12:27:54 AM - Unable to write data to the transport connection: An
existing connection was forcibly closed by the remote host.
After updating from Azure SDK2.5 to SDK 2.6, I had the same problem when trying publish to my Azure service from VS2013: Any deployment effort using Visual Studio fails after some minutes with 500 Internal server error.
As I found the reason is the very slow upload of the Azure package to the cloud - sometimes only between 30kB/s and 50kB/s. The deployment fails because of an timeout which also explains, that the Azure instance logs show no sign of any deployment...
Work around: Deploy from Azure storage
1: Package the Azure solution, either via VisualStudio or via command line:
MSBuild /t:Publish /p:TargetProfile=Cloud /P:Configuration=Release
2: Create an Azure storage container to upload your package to.
Continue using AzurePowerShell cmdlets:
3: Login
Add-AzureAccount
4: Upload the package to the your Azure storage container
$Ctx = New-AzureStorageContext -StorageAccountName "yourstoragename" -StorageAccountKey "yourkey"
Set-AzureStorageBlobContent -File "...\app.publish\yourservice.cspkg" -Container "yourazurestoragecontainer" -Blob "yourservice.cspkg" -Context $Ctx -Force
Determine the PackageURL of the uploaded package.
5: Deploy the cloud service referring to the package just uploaded to Azure cloud storage.
Set-AzureDeployment -Upgrade -Slot "Staging" -Package "PackageURL" -Configuration "PathToYourCloudConfiguration.cscfg" -label "SomeDeploymentInfo" -ServiceName "yourservicename" -Force
(Of course the entire process is scriptable. Kemp Brown wrote a great article: with a script you could adapt to explictly upload the package:
Continuous Delivery for Cloud Services in Azure)
Actually the problem was my network connection.
to identify this problem i created VM on azure with same windows 8.1 OS and same VS. i tried to deploy from there. deployment worked fine. latter I disconnected all other devices from my internet connection and i tried to publish from my machine. it worked !
so conclusion is slow internet connection or may be now we have less timeout time for publish from VS !
When I try to deploy my app locally I can't get it running. This is what it's telling me:
2014-10-24 13:16:08 Running command: "['C:\\Python27\\python.exe', 'C:\\Program Files (x86)\\Google\\google_appengine\\dev_appserver.py', '--skip_sdk_update_check=yes', '--port=3306', '--admin_port=8000', 'D:\\Documents\\Clever-CV Project\\wp39 - Copy']"
INFO 2014-10-24 13:16:15,315 devappserver2.py:733] Skipping SDK update check.
WARNING 2014-10-24 13:16:15,345 api_server.py:383] Could not initialize images API; you are likely missing the Python "PIL" module.
INFO 2014-10-24 13:16:15,368 api_server.py:171] Starting API server at: http://localhost:49717
INFO 2014-10-24 13:16:15,381 api_server.py:583] Applying all pending transactions and saving the datastore
INFO 2014-10-24 13:16:15,381 api_server.py:586] Saving search indexes
Traceback (most recent call last):
File "C:\Program Files (x86)\Google\google_appengine\dev_appserver.py", line 82, in <module>
_run_file(__file__, globals())
<--ommitted-->>
raise BindError('Unable to bind %s:%s' % self.bind_addr)
google.appengine.tools.devappserver2.wsgi_server.BindError: Unable to bind localhost:3306
2014-10-24 13:16:15 (Process exited with code 1)
And I am a noob - so there's a very good chance I did something stupid, but I'm at my wits end and have found everything I could online to try.
My SQL instance is running, the database passwords work and connect locally and to the remote app CloudSQL instance.
My app.yaml file has a new version name
the wordpress config file has the root names/passwords set-up correctly
The issue with running your app locally is in this part: '--port=3306' which is mysql's default port and you said mysql is already running which means that port is already taken and cannot be used by your app. Instead of 3306 try the default 8080 port and increase it by one (i.e. 8081, 8082, etc) in case you need to run multiple applications at once.