Nextcloud first installation - nextcloud

I'm tring to install nextcloud on my linux server, but I receive the error:
Internal Server Error
The server was unable to complete your request.
If this happens again, please send the technical details below to the server administrator.
More details can be found in the server log.
On nextcloud.log file I've this error:
"message":{
"Exception":"Doctrine\\DBAL\\Exception\\TableNotFoundException",
"Message":"An exception occurred while executing 'SELECT * FROM \"oc_appconfig\"':\n\nSQLSTATE[42P01]: Undefined table: 7 ERROR: relation \"oc_appconfig\" does not exist\nLINE 1: SELECT * FROM \"oc_appconfig\"\n ^",
"Code":0,
"Trace":[
{
"file":"\/www\/htdocs\/nextcloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/DBALException.php",
"line":169,
"function":"convertException",
"class":"Doctrine\\DBAL\\Driver\\AbstractPostgreSQLDriver",
"type":"->",
"args":[
"An exception occurred while executing 'SELECT * FROM \"oc_appconfig\"':\n\nSQLSTATE[42P01]: Undefined table: 7 ERROR: relation \"oc_appconfig\" does not exist\nLINE 1: SELECT * FROM \"oc_appconfig\"\n ^",
{
"errorInfo":[
"42P01",
7,
"ERROR: relation \"oc_appconfig\" does not exist\nLINE 1: SELECT * FROM \"oc_appconfig\"\n ^"
],
"__class__":"Doctrine\\DBAL\\Driver\\PDOException"
}
]
},
Why I've this error, if this is my first installation?

you should provide more information about your installation.
example: os, web server, DB server, php version etc.
But for me it looks like something went/is wrong with the DB server.
Is it accessible? If yes check if there is your DB.
Best regards
oBiE

Related

Blazor App - Error: Failed to complete negotiation with the server: Error: Forbidden

I have a Blazor App that runs perfectly well on localhost, however, when I deploy it to the server I get the following error:
Error: Failed to complete negotiation with the server: Error: Forbidden
Error: Failed to start the connection: Error: Forbidden
Error: Error: Forbidden
Error: Cannot send data if the connection is not in the 'Connected' State.
error comes from blazor.server.js.
I looked everywhere and there is no such error reported as far as I know.
Turns out, firewall was blocking it. Simply changing it's security to a lower level did the trick

Error while running query on Impala with Superset

I'm trying to connect impala to superset, and when I test the connection prints: "Seems OK!", and when I try to see databases on impala with the SQL Editor in the left side it shows all databases without problems.
Preview of Databases/Tables
But when i write a query and click on "Run Query", it gives the error: "Could not start SASL: b'Error in sasl_client_start (-1) SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Ticket expired)'"
Error running query
I'm running superset with SSL and in production mode (with Gunicorn) and Impala with SSL in a Kerberized Hadoop Cluster, and my impala database config is:
Impala Config
And in the extras I put:
{
"metadata_params": {},
"engine_params": {
"connect_args": {
"port": 21050,
"use_ssl": "True",
"ca_cert": "path/to/my/ca_cert.pem",
"auth_mechanism": "GSSAPI"
}
},
"metadata_cache_timeout": {},
"schemas_allowed_for_csv_upload": []
}
How can I solve this error? In my superset log it only shows:
Triggering query_id: 65
INFO:superset.views.core:Triggering query_id: 65
Query 65: Running query on a Celery worker
INFO:superset.views.core:Query 65: Running query on a Celery worker
Versions: Superset 0.36.0, Impyla 0.16.2
I was able to fix this error doing this steps:
1 - Created service user for celery-worker, created a kerberos ticket for him and created a crontab to renew the ticket.
2 - Runned celery worker from this service user, instead running from root.
3 - Killed an celery-worker that was running in another machine of my cluster
4 - Restarted Impala and Superset
I think this error ocurred because in some queries instead of use the celery worker in my superset machine, it was using the celery worker that was in another machine without a valid kerberos ticket. I could fix this error because when I was reading celery-worker log , it showed that a connection with the celery worker in other machine failed in a query running.

Airflow Adaptive Server connection failed

I want to connect my Airflow and Microsoft SQL Server. I configured my connection under 'connections' bar in 'Admin' box as mentioned in the following link:
http://airflow.apache.org/howto/manage-connections.html
But when I run my Dag task that is related to SQL server immedatly fails by following error:
[2019-03-28 16:16:07,439] {models.py:1788} ERROR - (18456, "Login failed for user 'XXXX'.DB-Lib error message 20018, severity 14:\nGeneral SQL Server error: Check messages from the SQL Server\nDB-Lib error message 20002, severity 9:\nAdaptive Server connection failed (***.***.***.28:1433)\n")
My code from DAG for Micrososft Sql Connection is following:
sql_command = """
select * from [sys].[tables]
"""
t3 = MsSqlOperator( task_id = 'run_test_proc',
mssql_conn_id = 'FIConnection',
sql = sql_command,
dag = dag)
I verified ip address and port number kind of configuration things by establishing connection through pymssql library from my local computer. Test code is following:
pymssql.connect(server="***.***.***.28:1433",
user="XXXX",
password="XXXXXX"
) as conn:
df = pd.read_sql("SELECT * FROM [sys].[tables]", conn)
print(df)
Could you please share if you have experienced this issue?
By the way I am using VirtualBox in Ubuntu 16.04 LTS
I had the same problem because freetds-dev was missing on linux:
apt-get install freetds-dev

SSL encryption error when installing SQL Server Express

I am attempting to install SQL Server Express Edition (64-bit) on my Windows 10 laptop. It is failing, apparently because of this:
2018-06-04 14:55:20.52 spid15s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
2018-06-04 14:55:20.52 spid15s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2018-06-04 14:55:20.52 spid15s Error: 17182, Severity: 16, State: 1.
2018-06-04 14:55:20.52 spid15s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
I do not know how to resolve this; can anyone help me out?
Resolved: for some reason using VPN to log into my employer's network did not allow me to install SQL Server Express. However, from their offices and on the company intranet the problem went away.

Wirecloud and IDM server hiccup

I linked wirecloud and Idm recently. When i login into wirecloud and i land into my wirecloud i got the following error:
Sorry, but the requested page is unavailable due to a server hiccup.
Our engineers have been notified, so check back later.
My idm configuration is:
URL
http://151.80.41.166:50002
Callback URL
http://151.80.41.166:50002/complete/fiware/
I cant get more error info
Exception Type: AuthStateMissing
Exception Value: Session value state missing.
Exception Location: /usr/local/lib/python2.7/site-packages/social_core/backends/oauth.py in validate_state, line 90
Python Executable: /usr/local/bin/python
Python Version: 2.7.14
Python Path:
['/opt/wirecloud_instance',
'/usr/local/lib/python27.zip',
'/usr/local/lib/python2.7',
'/usr/local/lib/python2.7/plat-linux2',
'/usr/local/lib/python2.7/lib-tk',
'/usr/local/lib/python2.7/lib-old',
'/usr/local/lib/python2.7/lib-dynload',
'/usr/local/lib/python2.7/site-packages']
The problem was i got in the same machine idm and Wirecloud and they use the same cookie.
I add the follow lines on settings.py
SESSION_COOKIE_NAME = "wcsessionid"
CSRF_COOKIE_NAME = "wccsrftoken"