How to perform maintenance tasks

Steps to reproduce

  1. Install oCIS as Systemd Setup ( https ://owncloud.dev/ocis/deployment/systemd/ )
  2. Try to run ocis commands

Expected behaviour

During upgrade from oCIS 3.0.0 to 4.0.0 i need to run “ocis migrate rebuild-jsoncs3-indexes”
I thought i run this command either as root or user ocis and the indexes are rebuilt

Actual behaviour

I cannot run it.
if i run as root (# ocis migrate rebuild-jsoncs3-indexes) i get “The jwt_secret has not been set properly in your config for sharing. Make sure your /root/.ocis/config config contains the proper values (e.g. by running ocis init or setting it manually in the config/corresponding environment variable).”

As i cannot login as user ocis i tried sudo (# sudo -u ocis /usr/local/bin/ocis migrate rebuild-jsoncs3-indexes) and got "The jwt_secret has not been set properly in your config for sharing. Make sure your /home/ocis/.ocis/config config contains the proper values (e.g. by running ocis init or setting it manually in the config/corresponding environment variable). "

i tried to setup the environment variables using “export” or just by definig them (f.e. OCIS_CONFIG_DIR=“/etc/ocis”
and get
"# echo $OCIS_CONFIG_DIR /etc/ocis " so it look fine.

Even if i run basic ocis commands, it always tells me no service found, also i can see in htop, that my service is running.

systemctl status ocis

● ocis.service - OCIS server
Loaded: loaded (/etc/systemd/system/ocis.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2023-09-05 07:23:16 CEST; 14h ago
Main PID: 538796 (ocis)
Tasks: 19 (limit: 9259)
Memory: 2.1G
CPU: 8min 45.909s
CGroup: /system.slice/ocis.service
└─538796 /usr/local/bin/ocis server

ocis version

Version: 4.0.0
Compiled: 2023-08-25 00:00:00 +0000 UTC

No running services found.

Thanks for any help!

Kind regards
Marc

Server configuration

Operating system: Debian 11

Web server: nginx

Database: n/a

PHP version: n/a

ownCloud version: oCIS 4.0.0

Updated from an older ownCloud or fresh install: Updated

Where did you install ownCloud from: official download portal

Signing status (ownCloud 9.0 and above):

Login as admin user into your ownCloud and access 
http://example.com/index.php/settings/integrity/failed 
paste the results into https://gist.github.com/ and puth the link here.

The content of config/config.php:

Log in to the web-UI with an administrator account and click on
'admin' -> 'Generate Config Report' -> 'Download ownCloud config report'
This report includes the config.php settings, the list of activated apps
and other details in a well sanitized form.

or 

If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your ownCloud installation folder

*ATTENTION:* Do not post your config.php file in public as is. Please use one of the above
methods whenever possible. Both, the generated reports from the web-ui and from occ config:list
consistently remove sensitive data. You still may want to review the report before sending.
If done manually then it is critical for your own privacy to dilligently
remove *all* host names, passwords, usernames, salts and other credentials before posting.
You should assume that attackers find such information and will use them against your systems.

List of activated apps:

If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your ownCloud installation folder.

Are you using external storage, if yes which one: local/smb/sftp/…

Are you using encryption: yes/no

Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/…

LDAP configuration (delete this part if not used)

With access to your command line run e.g.:
sudo -u www-data php occ ldap:show-config
from within your ownCloud installation folder

Without access to your command line download the data/owncloud.db to your local
computer or access your SQL server remotely and run the select query:
SELECT * FROM `oc_appconfig` WHERE `appid` = 'user_ldap';


Eventually replace sensitive data as the name/IP-address of your LDAP server or groups.

Client configuration

Browser:

Operating system:

Logs

Web server error log

Insert your webserver log here

ownCloud log (data/owncloud.log)

Insert your ownCloud log here

Browser log

Insert your browser log here, this could for example include:

a) The javascript console log
b) The network log 
c) ...
1 Like

What service are you talking about. This is different from the error message you posted before. What is the error message when you run with OCIS_CONFIG_DIR set?

1 Like

first of all, thank you for your reply!
i configured the variable now, but still cannot perform the task :wink: please see below what happens

root@debian-8gb-fsn1-1 ~ # export OCIS_CONFIG_DIR=“/etc/ocis”
root@debian-8gb-fsn1-1 ~ # echo $OCIS_CONFIG_DIR
/etc/ocis
root@debian-8gb-fsn1-1 ~ # ocis migrate rebuild-jsoncs3-indexes
com.owncloud.api.storage-system: service not found
root@debian-8gb-fsn1-1 ~ # systemctl status ocis.service
● ocis.service - OCIS server
Loaded: loaded (/etc/systemd/system/ocis.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2023-09-10 21:24:13 CEST; 15h ago
Main PID: 724553 (ocis)
Tasks: 24 (limit: 9259)
Memory: 673.7M
CPU: 3min 27.305s
CGroup: /system.slice/ocis.service
└─724553 /usr/local/bin/ocis server

Sep 11 12:51:56 debian-8gb-fsn1-1 ocis[724553]: {“level”:“warn”,“service”:“storage-system”,“pkg”:“rhttp”,“traceid”:“00000000000000000000000000000000”,“host”:“127.0.0.1”,“method”:“GET”,“uri”:“/data/spaces/jsoncs3-share-m>Sep 11 12:52:21 debian-8gb-fsn1-1 ocis[724553]: {“level”:“error”,“service”:“proxy”,“error”:“failed to verify access token: token is expired by 1.063607246s”,“authenticator”:“oidc”,“path”:”/graph/v1.0/me/drives",“time”:">Sep 11 12:52:21 debian-8gb-fsn1-1 ocis[724553]: {“level”:“error”,“service”:“gateway”,“pkg”:“rgrpc”,“traceid”:“00000000000000000000000000000000”,“error”:“internal error: gateway: error finding an auth provider for type: >Sep 11 12:52:21 debian-8gb-fsn1-1 ocis[724553]: {“level”:“error”,“service”:“gateway”,“pkg”:“rgrpc”,“traceid”:“00000000000000000000000000000000”,“error”:“internal error: gateway: error finding an auth provider for type: >Sep 11 12:52:21 debian-8gb-fsn1-1 ocis[724553]: {“level”:“warn”,“service”:“frontend”,“pkg”:“rhttp”,“traceid”:“00000000000000000000000000000000”,“time”:“2023-09-11T12:52:21.442988288+02:00”,“message”:“core access token n>Sep 11 12:52:21 debian-8gb-fsn1-1 ocis[724553]: {“level”:“error”,“service”:“gateway”,“pkg”:“rgrpc”,“traceid”:“00000000000000000000000000000000”,“error”:“internal error: gateway: error finding an auth provider for type: >Sep 11 12:52:25 debian-8gb-fsn1-1 ocis[724553]: {“level”:“warn”,“service”:“storage-system”,“pkg”:“rhttp”,“traceid”:“00000000000000000000000000000000”,“host”:“127.0.0.1”,“method”:“GET”,“uri”:”/data/spaces/jsoncs3-share-m>Sep 11 12:52:26 debian-8gb-fsn1-1 ocis[724553]: {“level”:“warn”,“service”:“storage-system”,“pkg”:“rhttp”,“traceid”:“00000000000000000000000000000000”,“host”:“127.0.0.1”,“method”:“GET”,“uri”:”/data/spaces/jsoncs3-share-m>Sep 11 12:52:56 debian-8gb-fsn1-1 ocis[724553]: {“level”:“warn”,“service”:“storage-system”,“pkg”:“rhttp”,“traceid”:“00000000000000000000000000000000”,“host”:“127.0.0.1”,“method”:“GET”,“uri”:”/data/spaces/jsoncs3-share-m>Sep 11 12:53:05 debian-8gb-fsn1-1 ocis[724553]: {“level”:“warn”,“service”:“storage-system”,“pkg”:“rhttp”,“traceid”:“00000000000000000000000000000000”,“host”:“127.0.0.1”,“method”:“GET”,“uri”:”/data/spaces/jsoncs3-share-m>

Ah I see. Did you follow the ocis upgrade guide? Upgrading from 3.0.0 to 4.0.0

If you don’t have any shares on your system you can ignore the error message.

2 Likes

Yes did follow each step, therefore i ran this command :wink:
I think i don’t have any share yet, maybe that’s the whole problem <.<
Thanks for your help, then i will ignore the error in my journactrl
Have a nice evening!

Cool. If you have no shares you have no problem :slight_smile: Just one more question: Did you run ocis with OCIS_RUN_SERVICES="gateway,nats,storage-system,storage-users" during the update?

1 Like

no, i did not start limited services.
instead i chose path B and disabled nginx for the upgrade process.
After journalctrl showed everything went smoothly and “ocis migrate decomposedfs -r list” gave me success for all users i started nginx again :wink:

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.