Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Looking for and not finding license.lic #814

Closed
unleashit opened this issue Mar 17, 2020 · 17 comments
Closed

Looking for and not finding license.lic #814

unleashit opened this issue Mar 17, 2020 · 17 comments
Labels
confirmed-bug Issues with confirmed bugs fixed Issues that fixed and released

Comments

@unleashit
Copy link

unleashit commented Mar 17, 2020

Do you want to request a feature or report a bug?

bug

What is the current behavior?

Getting an error in the document server logs that it can't find a license file.

I'm running the docker version of document server, nextcloud, the onlyoffice plugin. My setup was working perfectly for about two years and I'm not sure what could have changed to cause the issue other than recent upgrades to new versions of Document Server and Nextcloud (now 18).

I notice whenever I try to save the settings in Nextcloud, in addition to Error when trying to connect. Error occurred in the document service (Error while downloading the document file to be converted)., I get an error in the OO Document Server logs that it is looking for a license file but can't find it (see below). Thus is why I'm posting here and not on the repo for the plugin.

I've tried most of the posted solutions and none work. A few things I've done:

  • checked to see if the Nextcloud full text search plugin was activated (no), because it is a known issue with the plugin
  • verified that the document server container can access the nginx and nextcloud containers on the network
  • temporarily reverted some nginx settings that I changed when upgrading Nextcloud like X-Frame-Options "SAMEORIGIN"
  • nuked and recreated all containers, rebooted the server

The image I'm using is onlyoffice/documentserver:latest which is the community one so I'm assuming it shouldn't be looking for a license? Or if there should be a default one in there I did manually check the directory the error mentions and it's empty.

My setup is basically a modified version of: https://github.com/ONLYOFFICE/docker-onlyoffice-nextcloud. Everything is running (Nginx, Nextcloud, Document Server) on the same machine.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.

What is the expected behavior?

No errors

Did this work in previous versions of DocumentServer?

Yes

DocumentServer version:

5.5.0.165

Operating System:

Ubuntu 16

Browser version:

Firefox 74.0

[2020-03-17T19:28:37.028] [WARN] nodeJS - { Error: ENOENT: no such file or directory, open '/var/www/onlyoffice/documentserver/../Data/license.lic'
    at Object.openSync (fs.js:443:3)
    at Object.fs.openSync (pkg/prelude/bootstrap.js:490:32)
    at Object.readFileSync (fs.js:343:35)
    at Object.fs.readFileSync (pkg/prelude/bootstrap.js:686:36)
    at Object.exports.readLicense (/snapshot/server/build/server/Common/sources/license.js:0:0)
    at exports.readLicense.next (<anonymous>)
    at readLicense (/snapshot/server/build/server/DocService/sources/server.js:0:0)
    at readLicense.next (<anonymous>)
    at /snapshot/server/build/server/DocService/sources/server.js:0:0
    at Generator.next (<anonymous>)
    at onFulfilled (/snapshot/server/build/server/DocService/node_modules/co/index.js:65:19)
    at /snapshot/server/build/server/DocService/node_modules/co/index.js:54:5
    at new Promise (<anonymous>)
    at co (/snapshot/server/build/server/DocService/node_modules/co/index.js:50:10)
    at StatWatcher.updateLicense (/snapshot/server/build/server/DocService/sources/server.js:0:0)
    at StatWatcher.emit (events.js:198:13)
  errno: -2,
  syscall: 'open',
  code: 'ENOENT',
  path: '/var/www/onlyoffice/documentserver/../Data/license.lic' }
[2020-03-17T19:28:37.178] [WARN] nodeJS - Express server listening on port 8000 in production-linux mode
@ShockwaveNN
Copy link
Contributor

Hi, this is a known issue in our private bug tracker (44694)
And this error in logs should not have any impact on service, so I think it's better to ignore it until we fix it

@ShockwaveNN ShockwaveNN added the confirmed-bug Issues with confirmed bugs label Mar 18, 2020
@unleashit
Copy link
Author

Thanks for the reply. Are you sure it wouldn't impact the service? Because in my case it's not working and I've tried all of the usual stuff I could find. At this point, I guess I'll have to nuke my whole Nextcloud setup and start a new one because I've already spent a lot of time on this.

@ShockwaveNN
Copy link
Contributor

ShockwaveNN commented Mar 19, 2020

Because in my case it's not working

I think you may got some other troubles, as far as I known this error about license is harmless

But this error: Error when trying to connect. Error occurred in the document service (Error while downloading the document file to be converted). is not right.

Could you search logs for any other errors?
And can you access http://documentserver-url/healthcheck and see if it return true

@ShockwaveNN
Copy link
Contributor

Also error in logs with license is fixed by ONLYOFFICE/server@e85563f
and will be released in 5.5.1

@ShockwaveNN ShockwaveNN added the fixed Issues that fixed and released label Mar 19, 2020
@unleashit
Copy link
Author

Healthcheck returns true.

In converter/out.log (hadn't checked there before) I'm getting a bunch of:

[2020-03-19T19:32:13.405] [ERROR] nodeJS - error downloadFile:url=http://nginx-server/index.php/apps/onlyoffice/empty?doc=[base64stuffremovedIncaseItmatters];attempt=3;code:null;connect:null;(id=conv_check_1636191773_docx)
Error: Error response: statusCode:404 ;body:
<html>
<head><title>404 Not Found</title></head>
<body>
<center><h1>404 Not Found</h1></center>
<hr><center>nginx/1.17.9</center>
</body>
</html>

    at Request._callback (/snapshot/server/build/server/Common/sources/utils.js:0:0)
    at Request.init.self.callback (/snapshot/server/build/server/Common/node_modules/request/request.js:185:22)
    at Request.emit (events.js:198:13)
    at Request.<anonymous> (/snapshot/server/build/server/Common/node_modules/request/request.js:1154:10)
    at Request.emit (events.js:198:13)
    at IncomingMessage.<anonymous> (/snapshot/server/build/server/Common/node_modules/request/request.js:1076:12)
    at Object.onceWrapper (events.js:286:20)
    at IncomingMessage.emit (events.js:203:15)
    at endReadableNT (_stream_readable.js:1143:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)

In docservice/one.log (including the last archived version) other than the license error there is a Node warning about fs.watch availability:

[2020-03-17T17:23:11.868] [WARN] nodeJS - Plugins watch exception (https://nodejs.org/docs/latest/api/fs.html#fs_availability).

I confess that I don't fully understand how all these moving parts are supposed to work and unfortunately unless the above gives you any clues (and don't spend too much time on it) I'm just going to start over since I've already spent so much time on this. I'm sure it's related to upgrading from older versions of everything (it's been a cpl of years).

@ShockwaveNN
Copy link
Contributor

@unleashit I think your current problem is not related to DocumentServer per-se, but related to integration to nextcloud, so please create new issue in https://github.com/ONLYOFFICE/onlyoffice-nextcloud/

@ghost

This comment has been minimized.

@ShockwaveNN

This comment has been minimized.

@ghost

This comment has been minimized.

@ghost

This comment has been minimized.

@ShockwaveNN

This comment has been minimized.

@ghost

This comment has been minimized.

@ShockwaveNN

This comment has been minimized.

@ghost

This comment has been minimized.

@ShockwaveNN

This comment has been minimized.

@ghost

This comment has been minimized.

@ShockwaveNN
Copy link
Contributor

DocumentServer 5.5.1 released. This issue should be fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
confirmed-bug Issues with confirmed bugs fixed Issues that fixed and released
Projects
None yet
Development

No branches or pull requests

2 participants