Git Product home page Git Product logo

leihs-instance's Introduction

leihs

This is the top level project for leihs (version 4).

leihs -- the equipment booking and inventory management system

leihs is a system with which universities or other organizations can manage, book, lend and procure their equipment (and software). People can place reservations/bookings on items and then pick them up at e.g. a reservation desk. The system keeps track of who has which items and gives equipment managers time to worry about other things. Besides, the leihs system features a module for budgeting procurements and supporting the procurement process of existing and new equipment.

Live demo

You can try out a live installation of leihs (the address is below). It's always pointing to the latest stable development release. If the demo happens to be down, please make an issue.

Demo data is deleted and reset every 24 hours. It may also be deleted at any time during the day as deployment to the demo server is part of our continuous testing / deployment workflow.

The demo installation is located at http://demo.leihs.zhdk.ch.

For login details see here. For the description of the roles tight to the specific login users see here.

Features

An up-to-date, human-readable specification of all our scenarios is to be found here.

Wiki

All the important information is to be found here.

Issues

All present and past issues are tracked, discussed and dealt with here.

Browsers

Firefox, Chrome and Safari are the only supported browsers.

Support

If you are having troubles with the deployment, setting up the development environment or encounter bugs, please first take a look at our existing issue list. If you can't find an answer to your problem or question, then kindly make a new issue. We will occasionally take a look at it, while we don't guarantee any particular response time from our side.

In case of our inability to support you, we encourage you or your organisation to find a suitable partner to support you. We at ZHdK do not feel obliged in any way to offer any kind of support.

References (Who uses leihs?)

leihs is in use at several universities and organizations.

leihs Blog

Not maintained anymore, but you can maybe find some useful information there.

Copyright and license

leihs is (C)

leihs is Free Software under the GNU General Public License (GPL) v3, see the included LICENSE file for license details.

leihs-instance's People

Contributors

belafonte avatar eins78 avatar nimaai avatar sedurodotcom avatar urs-van-binsbergen avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

leihs-instance's Issues

Deployment not working

Whenever I try to deploy leihs from my controll mashine with docker I get an ssh error:
Failed to connect to the host via ssh:

Warning: Permanently added 'host,ip' (ECDSA) to the list of known hosts.
root@host: Permission denied (publickey).

PLAY RECAP *******************************************************************************************************************
host : ok=0    changed=0    unreachable=1    failed=0   

Outside of the deploymet process the ssh connection is working fine and ssh-agent-forwarding is also enabled.

I also tried the dockerless deployment but sadly that doesn't seem to work ether.
It gives me the following output but after that nothing happends and I get droped back into my shell

+ git submodule update --recursive --init --force --quiet
+ cd leihs/deploy
+ bin/ansible-playbook -i ../../hosts -e use_s3_build_cache=yes deploy_play.yml
✪ virtualenv: preparing…

My host is on debian 10 (buster) and my contoll mashine on debian testing (bullseye)

Leihs version 6.0.0: TASK [leihs-mail-install : create jar] error

Hi there it's me again :)

There seems to be a problem with the task "TASK [leihs-mail-install : create jar]" here is a snippet of the error message:

TASK [leihs-mail-install : create jar] ************************************************************
fatal: [host]: FAILED! => {
    "changed": true,
    "cmd": "DEPLOY_DIR='/home/user/xxx_hosting/leihs/deploy'\nPROJECT_DIR=\"${DEPLOY_DIR}/../mail\"\n${PROJECT_DIR}/bin/build\n",
    "delta": "0:00:01.728208",
    "end": "2021-05-26 09:07:55.872213",
    "rc": 1,
    "start": "2021-05-26 09:07:54.144005"
}

STDOUT:

PWD: /home/user/xxx_hosting/leihs/mail
BUILD_CACHE_DISABLED=NO
INFO: checking clean working_tree in /home/user/xxx_hosting/leihs/mail 
LOCAL_CACHED_ARTEFACT_PATH: /home/user/xxx_hosting/tmp/build_cache/leihs-mail_83db748459816530c20763e93d5391d9261bf3ee.jar
INFO: locally cached artefact found, extracting, and caching ...


STDERR:

+ PROJECT_NAME=leihs-mail
+++ dirname /home/user/xxx_hosting/leihs/deploy/../mail/bin/build
++ cd -- /home/user/xxx_hosting/leihs/deploy/../mail/bin
++ cd ..
++ pwd -P
+ PROJECT_DIR=/home/user/xxx_hosting/leihs/mail
+ ARTEFACT_PATH=/home/user/xxx_hosting/leihs/mail/target/leihs-mail.jar
++ git -C /home/user/xxx_hosting/leihs/mail log -n 1 HEAD --pretty=%T
+ DIGEST=83db748459816530c20763e93d5391d9261bf3ee
+ LOCAL_CACHE_DIR=/home/user/xxx_hosting/tmp/build_cache
+ LOCAL_CACHED_ARTEFACT_PATH=/home/user/xxx_hosting/tmp/build_cache/leihs-mail_83db748459816530c20763e93d5391d9261bf3ee.jar
+ S3_CACHED_ARTEFACT_NAME=leihs-mail_83db748459816530c20763e93d5391d9261bf3ee.jar
+ BUILD_CACHE_DISABLED=NO
+ set +x
<internal:/usr/lib/ruby/3.0.0/rubygems/core_ext/kernel_require.rb>:85:in `require': cannot load such file -- bundler/inline (LoadError)
	from <internal:/usr/lib/ruby/3.0.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
	from ./bin/s3-cache-helper:3:in `<main>'


MSG:

non-zero return code

At first I thought it might be something with a missing installation of Ruby 3.0.0 on my server, but that does not seem to be the problem. Then i installed bundler via gem, but this didn't help either. The server is running Ubuntu 20.04.2 LTS.

Kind regards
-befrog

Deployment not working - error in TASK [leihs-my-install : create jar]

Hello,

I have been trying to deploy leihs with the following:

  • control machine Ubuntu Server 18.04
  • host machine: Debian 10

I am using docker as the deploy method.
The process is failing creating this jar and the problem seems to be lein. I already looked into the resolved issues (#15 seems similar, but in docker deploy script there is no use_s3_build_cache=yes as recommended here ), but I am not sure where to install lein - do I have to change the Dockerfile?

I am not sure which version of leihs was downloaded, but probably the latest.

Do you have any suggestions how to solve this?

Thanks in advance.

Jan

TASK [leihs-my-install : create jar] **************************************************************
fatal: TASK [leihs-my-install : create jar] ********************************************************
fatal: [leihs.xxxx.de]: FAILED! => {
    "changed": true,
    "cmd": "DEPLOY_DIR='/leihs-instance/leihs/deploy'\nPROJECT_DIR=\"${DEPLOY_DIR}/../my\"\n${PROJECT_DIR}/bin/build\n",
    "delta": "0:03:21.305302",
    "end": "2021-06-23 13:22:54.093827",
    "rc": 1,
    "start": "2021-06-23 13:19:32.788525"
}

[here was much code  that has 

./bootstrap-theme-leihs/build/bootstrap-leihs.js.map
./bootstrap-theme-leihs/build/bootstrap-leihs.js
./bootstrap-theme-leihs/build/bootstrap-leihs.css
./bootstrap-theme-leihs/build/bootstrap-leihs.css.map
INFO: S3 env vars are not defined; exiting immediatelly without error
/leihs-instance/leihs/my
OK ✔
build error!


STDERR:

+ PROJECT_NAME=leihs-my
+++ dirname /leihs-instance/leihs/deploy/../my/bin/build
++ cd -- /leihs-instance/leihs/deploy/../my/bin
++ cd ..
++ pwd -P
+ PROJECT_DIR=/leihs-instance/leihs/my
+ UI_DIR=/leihs-instance/leihs/my/leihs-ui
+ ARTEFACT_PATH=/leihs-instance/leihs/my/target/leihs-my.jar
++ git -C /leihs-instance/leihs/my log -n 1 HEAD --pretty=%T
+ DIGEST=833636263662e9d7437494510354735bc9dd7414
+ LOCAL_CACHE_DIR=/home/kopetz/tmp/build_cache
+ LOCAL_CACHED_ARTEFACT_PATH=/home/kopetz/tmp/build_cache/leihs-my_833636263662e9d7437494510354735bc9dd7414.jar
+ S3_CACHED_ARTEFACT_NAME=leihs-my_833636263662e9d7437494510354735bc9dd7414.jar
+ BUILD_CACHE_DISABLED=NO
+ set +x
+ PROJECT_NAME=leihs-ui
+++ dirname ./leihs-ui/bin/build
++ cd -- ./leihs-ui/bin
++ cd ..
++ pwd -P
+ PROJECT_DIR=/leihs-instance/leihs/my/leihs-ui
+ ARTEFACT_NAME=leihs-ui
+ ARTEFACT_PATHS='./dist ./bootstrap-theme-leihs/build'
++ git -C /leihs-instance/leihs/my/leihs-ui log -n 1 HEAD --pretty=%T
+ DIGEST=7cc8dd6af7c75220bdecb1805514b7fdb5f12187
+ LOCAL_CACHE_DIR=/home/kopetz/tmp/build_cache
+ LOCAL_CACHED_ARTEFACT_PATH=/home/kopetz/tmp/build_cache/leihs-ui_7cc8dd6af7c75220bdecb1805514b7fdb5f12187.tgz
+ S3_CACHED_ARTEFACT_NAME=leihs-ui_7cc8dd6af7c75220bdecb1805514b7fdb5f12187.tgz
+ BUILD_CACHE_DISABLED=NO
+ set +x
++ dirname ./bin/build-core
+ cd ./bin/..
+ ./bin/deps-install
++ dirname ./bin/deps-install
+ cd ./bin/..
+ cd bootstrap-theme-leihs
+ npm ci --no-audit
+ npm run ensure-sass
+ cd -
+ npm ci --no-audit
+ cd -
+ npm run build:theme
WARNING: The `bg-variant` mixin has been deprecated as of v4.4.0. It will be removed entirely in v5.
         on line 8 of node_modules/bootstrap/scss/mixins/_deprecate.scss, in mixin `deprecate`
         from line 15 of node_modules/bootstrap/scss/mixins/_background-variant.scss, in mixin `bg-variant`
         from line 32 of stdin

WARNING: The `bg-variant` mixin has been deprecated as of v4.4.0. It will be removed entirely in v5.
         on line 8 of node_modules/bootstrap/scss/mixins/_deprecate.scss, in mixin `deprecate`
         from line 15 of node_modules/bootstrap/scss/mixins/_background-variant.scss, in mixin `bg-variant`
         from line 33 of stdin

Browserslist: caniuse-lite is outdated. Please run the following command: `npm update`
You did not set any plugins, parser, or stringifier. Right now, PostCSS does nothing. Pick plugins for your case on https://www.postcss.parts/ and use them in postcss.config.js.
You did not set any plugins, parser, or stringifier. Right now, PostCSS does nothing. Pick plugins for your case on https://www.postcss.parts/ and use them in postcss.config.js.
You did not set any plugins, parser, or stringifier. Right now, PostCSS does nothing. Pick plugins for your case on https://www.postcss.parts/ and use them in postcss.config.js.
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db

Why you should do it regularly:
https://github.com/browserslist/browserslist#browsers-data-updating
+ npm run build:ssr
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db

Why you should do it regularly:
https://github.com/browserslist/browserslist#browsers-data-updating

  `@babel/polyfill` is deprecated. Please, use required parts of `core-js`
  and `regenerator-runtime/runtime` separately
+ cd -
/leihs-instance/leihs/deploy/../my/bin/build: line 37: lein: command not found


MSG:

non-zero return code

Leihs deploy-from-docker stuck at [leihs-mail-install : create jar]

Hi there,
When I run the deploy-from-docker file everything seems to be fine until the Script is trying to execute the [leihs-mail-install : create jar] task. It just gets stuck. At first, I thought it might just take a while to install but after about 4-5h I was confident something was wrong. Here is a snippet of the deploy script with 5 times verbose turned on:

TASK [leihs-mail-install : create jar] ****************************************
task path: /leihs-instance/leihs/deploy/roles/leihs-mail-install/tasks/jar.yml:1
File lookup using /leihs-instance/leihs/deploy/helpers/build-artefact-with-s3-cache.bash as file
Using module file /usr/local/lib/python2.7/dist-packages/ansible/modules/commands/command.py
<localhost> ESTABLISH LOCAL CONNECTION FOR USER: root
<localhost> EXEC /bin/sh -c '/usr/bin/python && sleep 0'

There does not seem to be an error there, could you please take a look at that?

Deployment not working

Hello,

I have been trying to deploy leihs with the following:

  • control machine Ubuntu Desktop 20.04
  • host machine: Ubuntu Server 18.04
  • leihs updated to the last master version

I did had some of the problems in the closed issues, but I do not know how to solve this one.

Here the last part of the error I get, let me know if you need more details:

WARNING: The `bg-variant` mixin has been deprecated as of v4.4.0. It will be removed entirely in v5.
         on line 8 of node_modules/bootstrap/scss/mixins/_deprecate.scss, in mixin `deprecate`
         from line 15 of node_modules/bootstrap/scss/mixins/_background-variant.scss, in mixin `bg-variant`
         from line 32 of stdin

WARNING: The `bg-variant` mixin has been deprecated as of v4.4.0. It will be removed entirely in v5.
         on line 8 of node_modules/bootstrap/scss/mixins/_deprecate.scss, in mixin `deprecate`
         from line 15 of node_modules/bootstrap/scss/mixins/_background-variant.scss, in mixin `bg-variant`
         from line 33 of stdin

Browserslist: caniuse-lite is outdated. Please run the following command: `npm update`
You did not set any plugins, parser, or stringifier. Right now, PostCSS does nothing. Pick plugins for your case on https://www.postcss.parts/ and use them in postcss.config.js.
You did not set any plugins, parser, or stringifier. Right now, PostCSS does nothing. Pick plugins for your case on https://www.postcss.parts/ and use them in postcss.config.js.
You did not set any plugins, parser, or stringifier. Right now, PostCSS does nothing. Pick plugins for your case on https://www.postcss.parts/ and use them in postcss.config.js.
+ npm run build:ssr
+ cd -
/leihs-instance/leihs/deploy/../my/bin/build: line 37: lein: command not found


MSG:

non-zero return code

PLAY RECAP ****************************************************************************
192.168.2.153              : ok=114  changed=26   unreachable=0    failed=1    skipped=18   rescued=0    ignored=0 

Update to 6.4.1

Hi,

Please, could you update "master" to 6.4.1

thx

regards
Mario

Leihs does not come up again after system reboot

Leihs does not come up again after system reboot:

Jan 31 15:22:13 leihs ruby[500]: : CREATE DATABASE "leihs" ENCODING = 'unicode'
Jan 31 15:22:13 leihs ruby[500]: Couldn't create database for {"adapter"=>"postgresql", "host"=>"localhost", "port"=>5432, "pool"=>25, "encoding"=>"unicode", "username"=>"root", "password"=>"root", "database"=>"leihs"}
Jan 31 15:22:13 leihs ruby[500]: rake aborted!
Jan 31 15:22:13 leihs ruby[500]: ActiveRecord::StatementInvalid: PG::DuplicateDatabase: FEHLER:  Datenbank »leihs« existiert bereits
Jan 31 15:22:13 leihs ruby[500]: : CREATE DATABASE "leihs" ENCODING = 'unicode'
Jan 31 15:22:13 leihs ruby[500]: /home/leihs-database/.rubies/ruby-2.4.2/bin/bundle:23:in `load'
Jan 31 15:22:13 leihs ruby[500]: /home/leihs-database/.rubies/ruby-2.4.2/bin/bundle:23:in `<main>'
Jan 31 15:22:13 leihs ruby[500]: PG::DuplicateDatabase: FEHLER:  Datenbank »leihs« existiert bereits
Jan 31 15:22:13 leihs ruby[500]: /home/leihs-database/.rubies/ruby-2.4.2/bin/bundle:23:in `load'
Jan 31 15:22:13 leihs ruby[500]: /home/leihs-database/.rubies/ruby-2.4.2/bin/bundle:23:in `<main>'
Jan 31 15:22:13 leihs ruby[500]: Tasks: TOP => db:create
Jan 31 15:22:13 leihs ruby[500]: (See full trace by running task with --trace)
Jan 31 15:22:13 leihs systemd[1]: leihs-migration.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 15:22:13 leihs systemd[1]: Failed to start Leihs Migration Service.
Jan 31 15:22:13 leihs systemd[1]: Dependency failed for Leihs Legacy Service.
Jan 31 15:22:13 leihs systemd[1]: leihs-legacy.service: Job leihs-legacy.service/start failed with result 'dependency'.
Jan 31 15:22:13 leihs systemd[1]: leihs-migration.service: Unit entered failed state.
Jan 31 15:22:13 leihs systemd[1]: leihs-migration.service: Failed with result 'exit-code'.

Feedback: Docker-based build&deploy (not hosting)

The deployment of leihs can now be run inside a Docker container that includes everything needed to build and deploy leihs (Java, node.js, ansible, etc).
As a side effect, that should solve most of the various issues that were reported (but we did not have resources to solve them). It might even work on Windows 😅 (but I have not tried).

I'll leave this issue open for a while as central place to provide feedback and discuss of there are any problems with this approach.
If there are still problems with setting up a new instance from scratch (according to the GUIDE.md) they can also be reported here – another upside of using Docker for the build environment is that it's much more reproducible, so problems can be debugged and fixed faster.


Help

Update leihs to 5.2.0:

cd leihs && git fetch && git checkout 5.2.0 && cd -

Update leihs-instance using git (if you've forked this repo):

git remote add upstream https://github.com/leihs/leihs-instance
git pull upstream master

Or, update leihs-instance without using git:

curl -L https://github.com/leihs/leihs-instance/archive/master.tar.gz | tar -xzv --strip=1

Those are the interesting parts:

Fehler beim Ausführen von ./scripts/deploy-from-docker

Hello,
i have a problem with one script here: when i'm at the installation step:

./scripts/deploy-from-docker

i am getting:
[...]
`Step 22/22 : WORKDIR /leihs/deploy
---> Using cache
---> 23121723ade7
Successfully built 23121723ade7
Successfully tagged leihs/ansible-controller:latest

PLAY [all] ********************************************************************************************************************************************************************************************************************************************************************

TASK [install system python] **************************************************************************************************************************************************************************************************************************************************
fatal: [servername]: UNREACHABLE! => {
"changed": false,
"unreachable": true
}

MSG:

Failed to connect to the host via ssh: Warning: Permanently added 'servername,ip' (ECDSA) to the list of known hosts.
root@servername: Permission denied (publickey,password).
`
If i test it with ssh root@servername i get in (with publickey, not with password - for test i deactivated the passphrase too, but nevertheless i get this message...

With ./scripts/deploy-from-docker -vvv i get an actually clear failure:

debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /root/.ssh/id_rsa
debug3: no such identity: /root/.ssh/id_rsa: No such file or directory
debug1: Trying private key: /root/.ssh/id_dsa
debug3: no such identity: /root/.ssh/id_dsa: No such file or directory
debug1: Trying private key: /root/.ssh/id_ecdsa
debug3: no such identity: /root/.ssh/id_ecdsa: No such file or directory
debug1: Trying private key: /root/.ssh/id_ed25519
debug3: no such identity: /root/.ssh/id_ed25519: No such file or directory
debug1: Trying private key: /root/.ssh/id_xmss
debug3: no such identity: /root/.ssh/id_xmss: No such file or directory
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
root@servername: Permission denied (publickey,password).

I tried to uncommand
IdentityFile ~/.ssh/id_rsa PermitRootLogin yes
in the /etc/ssh/ssh_conf
and
PasswordAuthentication yes PermitRootLogin yes RSAAuthentication yes PubkeyAuthentication yes
in the /etc/ssh/sshd_conf
and
i set all right als /root/.ssh/* correct (private keys only owner, pubkey readable for all, etc...) but still the failure appears...
I don't get why the script actually have to ssh to its own...

ssh "${LEIHS_HOST_USER}@${LEIHS_HOSTNAME}" -- 'test $(id -u) -eq 0 && echo OK || sudo echo OK'

gives me from the beginning an "OK"

Have anyone an idea?

Thanks
xyllyxy

settings_file_path seems to not be used anywhere

Maybe I have overlooked it but I cannot find where the settings_file_path in the examples/host_vars_example.yml is used.
If it's not needed anymore I think it would be best to update documentation and examples.

Update/Deployment fails: Collecting cryptography==36.0.1

Hello,
when updating our instance I get the following error when executing ./scripts/deploy-from-docker:

Step 15/22 : COPY ["./ansible-requirements.txt", "/tmp/ansible-requirements.txt"]
 ---> f04c01167d80
Step 16/22 : RUN pip install -r "/tmp/ansible-requirements.txt" && rm "/tmp/ansible-requirements.txt"
 ---> Running in cac522e309ef
Collecting ansible==4.10.0 (from -r /tmp/ansible-requirements.txt (line 1))
  Downloading https://files.pythonhosted.org/packages/fd/f8/071905c6a67592d0852a9f340f6ab9226861eeeb97fdf4068642b22edcf3/ansible-4.10.0.tar.gz (36.8MB)
Collecting ansible-core==2.11.9 (from -r /tmp/ansible-requirements.txt (line 2))
  Downloading https://files.pythonhosted.org/packages/68/b1/551c421c3ce322ccf221b619ea61ec862dc34b08ebb76580fd71709c5e36/ansible-core-2.11.9.tar.gz (7.1MB)
Collecting cffi==1.15.0 (from -r /tmp/ansible-requirements.txt (line 3))
  Downloading https://files.pythonhosted.org/packages/26/28/fb01ff898aa7c93e4774799b3dc0a3693cfee48c5ea4e524ce30e6b10e7e/cffi-1.15.0-cp27-cp27mu-manylinux1_x86_64.whl (393kB)
Collecting cryptography==36.0.1 (from -r /tmp/ansible-requirements.txt (line 4))
  Could not find a version that satisfies the requirement cryptography==36.0.1 (from -r /tmp/ansible-requirements.txt (line 4)) (from versions: 0.1, 0.2, 0.2.1, 0.2.2, 0.3, 0.4, 0.5, 0.5.1, 0.5.2, 0.5.3, 0.5.4, 0.6, 0.6.1, 0.7, 0.7.1, 0.7.2, 0.8, 0.8.1, 0.8.2, 0.9, 0.9.1, 0.9.2, 0.9.3, 1.0, 1.0.1, 1.0.2, 1.1, 1.1.1, 1.1.2, 1.2, 1.2.1, 1.2.2, 1.2.3, 1.3, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.4, 1.5, 1.5.1, 1.5.2, 1.5.3, 1.6, 1.7, 1.7.1, 1.7.2, 1.8, 1.8.1, 1.8.2, 1.9, 2.0, 2.0.1, 2.0.2, 2.0.3, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2, 2.2.1, 2.2.2, 2.3, 2.3.1, 2.4, 2.4.1, 2.4.2, 2.5, 2.6, 2.6.1, 2.7, 2.8, 2.9, 2.9.1, 2.9.2, 3.0, 3.1, 3.1.1, 3.2, 3.2.1, 3.3, 3.3.1, 3.3.2)
No matching distribution found for cryptography==36.0.1 (from -r /tmp/ansible-requirements.txt (line 4))

I don't understand the error, cryptography 36.0.1 seem's valid...

Any help is kindly appreciated!
Matthias

Syntax error in tasks/service.yml while deploying v7

While deploying v7 I get this error:

[WARNING]: While constructing a mapping from /…/leihs/deploy/roles/leihs-legacy-install/tasks/service.yml, line 1, column 3, found a duplicate dict key (args). Using last defined value only.

Deployment not working

Hello,

I have been trying to deploy leihs again on a new server with the following:

  • control machine Ubuntu Desktop 20.04
  • host machine: Ubuntu Server 18.04
  • leihs updated to the last master version

This time the error is about npm, which is not found by one the of scripts (leihs/my/leihs-ui/bin/deps-install).
Making a script manually and running it into the server, finds npm without problems.

Thanks for the help.

Below the log:

`TASK [leihs-my-install : create jar] ********************************************************************************************************************************************
fatal: [leihs.hochschule-rhein-waal.de]: FAILED! => {
"changed": true,
"cmd": "DEPLOY_DIR='/home/satsha/Documents/leihs.hochschule-rhein-waal.de_hosting/leihs/deploy'\nPROJECT_DIR="${DEPLOY_DIR}/../my"\n${PROJECT_DIR}/bin/build\n",
"delta": "0:00:01.646762",
"end": "2021-06-14 19:56:17.554710",
"rc": 1,
"start": "2021-06-14 19:56:15.907948"
}

STDOUT:

PWD: /home/satsha/Documents/leihs.hochschule-rhein-waal.de_hosting/leihs/my
BUILD_CACHE_DISABLED=NO
INFO: checking clean working_tree in /home/satsha/Documents/leihs.hochschule-rhein-waal.de_hosting/leihs/my
LOCAL_CACHED_ARTEFACT_PATH: /home/satsha/Documents/leihs.hochschule-rhein-waal.de_hosting/tmp/build_cache/leihs-my_fecf8df196351c3c0256b4bf67a4cb216cba3a12.jar
S3_CACHED_ARTEFACT_NAME: leihs-my_fecf8df196351c3c0256b4bf67a4cb216cba3a12.jar
INFO: trying to download from S3 cache
WARN: S3 env vars are not defined; exiting immediatelly without error
INFO: no cached artefact found: building, packing, and caching ...
PWD: /home/satsha/Documents/leihs.hochschule-rhein-waal.de_hosting/leihs/my/leihs-ui
BUILD_CACHE_DISABLED=NO
INFO: checking clean working_tree in /home/satsha/Documents/leihs.hochschule-rhein-waal.de_hosting/leihs/my/leihs-ui
LOCAL_CACHED_ARTEFACT_PATH: /home/satsha/Documents/leihs.hochschule-rhein-waal.de_hosting/tmp/build_cache/leihs-ui_dd451b13830662189a1c066a546336a4f775ac72.tgz
S3_CACHED_ARTEFACT_NAME: leihs-ui_dd451b13830662189a1c066a546336a4f775ac72.tgz
INFO: trying to download from S3 cache
WARN: S3 env vars are not defined; exiting immediatelly without error
INFO: no cached artefact found: building, packing, and caching ...
build error!

STDERR:

  • PROJECT_NAME=leihs-my
    +++ dirname /home/satsha/Documents/leihs.hochschule-rhein-waal.de_hosting/leihs/deploy/../my/bin/build
    ++ cd -- /home/satsha/Documents/leihs.hochschule-rhein-waal.de_hosting/leihs/deploy/../my/bin
    ++ cd ..
    ++ pwd -P
  • PROJECT_DIR=/home/satsha/Documents/leihs.hochschule-rhein-waal.de_hosting/leihs/my
  • UI_DIR=/home/satsha/Documents/leihs.hochschule-rhein-waal.de_hosting/leihs/my/leihs-ui
  • ARTEFACT_PATH=/home/satsha/Documents/leihs.hochschule-rhein-waal.de_hosting/leihs/my/target/leihs-my.jar
    ++ git -C /home/satsha/Documents/leihs.hochschule-rhein-waal.de_hosting/leihs/my log -n 1 HEAD --pretty=%T
  • DIGEST=fecf8df196351c3c0256b4bf67a4cb216cba3a12
  • LOCAL_CACHE_DIR=/home/satsha/Documents/leihs.hochschule-rhein-waal.de_hosting/tmp/build_cache
  • LOCAL_CACHED_ARTEFACT_PATH=/home/satsha/Documents/leihs.hochschule-rhein-waal.de_hosting/tmp/build_cache/leihs-my_fecf8df196351c3c0256b4bf67a4cb216cba3a12.jar
  • S3_CACHED_ARTEFACT_NAME=leihs-my_fecf8df196351c3c0256b4bf67a4cb216cba3a12.jar
  • BUILD_CACHE_DISABLED=NO
  • set +x
  • PROJECT_NAME=leihs-ui
    +++ dirname ./leihs-ui/bin/build
    ++ cd -- ./leihs-ui/bin
    ++ cd ..
    ++ pwd -P
  • PROJECT_DIR=/home/satsha/Documents/leihs.hochschule-rhein-waal.de_hosting/leihs/my/leihs-ui
  • ARTEFACT_NAME=leihs-ui
  • ARTEFACT_PATHS='./dist ./bootstrap-theme-leihs/build'
    ++ git -C /home/satsha/Documents/leihs.hochschule-rhein-waal.de_hosting/leihs/my/leihs-ui log -n 1 HEAD --pretty=%T
  • DIGEST=dd451b13830662189a1c066a546336a4f775ac72
  • LOCAL_CACHE_DIR=/home/satsha/Documents/leihs.hochschule-rhein-waal.de_hosting/tmp/build_cache
  • LOCAL_CACHED_ARTEFACT_PATH=/home/satsha/Documents/leihs.hochschule-rhein-waal.de_hosting/tmp/build_cache/leihs-ui_dd451b13830662189a1c066a546336a4f775ac72.tgz
  • S3_CACHED_ARTEFACT_NAME=leihs-ui_dd451b13830662189a1c066a546336a4f775ac72.tgz
  • BUILD_CACHE_DISABLED=NO
  • set +x
    ++ dirname ./bin/build-core
  • cd ./bin/..
  • ./bin/deps-install
    ++ dirname ./bin/deps-install
  • cd ./bin/..
  • cd bootstrap-theme-leihs
  • npm ci --no-audit
    ./bin/deps-install: line 12: npm: command not found

MSG:

non-zero return code

PLAY RECAP **********************************************************************************************************************************************************************
leihs.hochschule-rhein-waal.de : ok=116 changed=26 unreachable=0 failed=1 skipped=18 rescued=0 ignored=0
`

open-vm-tools-dkms in Ubuntu 18.04

The package open-vm-tools-dkms is not available in Ubuntu 18.04 and there is no chance to customize the setup. If I delete the line - open-vm-tools-dkms in leihs/deploy/roles/os-setup/tasks/vmware.yml It is always overwritten.

TASK [os-setup : install vmware tools] ******************************************************************************************* [DEPRECATION WARNING]: Invoking "apt" only once while using a loop via squash_actions is deprecated. Instead of using a loop to supply multiple items and specifying name: {{item}}, please use name: [u'open-vm-tools', u'open-vm-tools-dkms']` and remove
the loop. This feature will be removed in version 2.11. Deprecation warnings can be disabled by setting
deprecation_warnings=False in ansible.cfg.
failed: [XXX] (item=[u'open-vm-tools', u'open-vm-tools-dkms']) => changed=false
item:

  • open-vm-tools
  • open-vm-tools-dkms
    msg: No package matching 'open-vm-tools-dkms' is available

PLAY RECAP ***********************************************************************************************************************
XXX : ok=28 changed=4 unreachable=0 failed=1`

Failed task: Add root postgresql user during deployment

Ansible deployment fails with

TASK [postgresql : add root postgresql user] *********************************************************************************************************************************************************
fatal: [192.168.178.28]: FAILED! => {"changed": false, "msg": "Failed to create remote module tmp path at dir /tmp/ansible_leihs_deploy with prefix ansible-moduletmp-1543145348.23-: [Errno 13] Permission denied: '/tmp/ansible_leihs_deploy/ansible-moduletmp-1543145348.23-g0zrXx'"}

PLAY RECAP *******************************************************************************************************************************************************************************************
192.168.178.28             : ok=27   changed=5    unreachable=0    failed=1

Occurs with fresh virtual machines in Ubuntu 18.04 and Debian 9.6.0 (both amd64). Deployment via root user to local virtual machines for testing purposes.

Can't set default language

Hi,

how do I set the default Language? It seems that the permissions appear to be bugged. When I try changing the language settings via the admin pannel it says that I " [...] don't have appropriate permission to perform this operation".
In addition the site seems to be a mixture of English and German words, witch will be worrying for most users, do you have a fix for that?

Kind regards
-befrog

Deployment not working (mimemagic (0.3.0) - version could not be found)

Hi,
I've got a problem installing leihs.
Following the "leihs Hosting Guide", I get the following error (./scripts/deploy-from-docker):

TASK [leihs-legacy-install : install bundler and bundle] ***********************
fatal: [....de]: FAILED! => {
    "changed": true, 
    "cmd": "set -eux\n export PATH=$HOME/.rubies/ruby-2.6.6/bin:$PATH\n which gem\n gem install bundler\n cd /leihs/legacy\n bundle install --retry=12 --without development --without test", 
    "delta": "0:00:24.507679", 
    "end": "2021-03-25 13:41:12.534025", 
    "rc": 7, 
    "start": "2021-03-25 13:40:48.026346"
}

STDOUT:

/home/leihs-legacy/.rubies/ruby-2.6.6/bin/gem
Successfully installed bundler-2.2.15
Parsing documentation for bundler-2.2.15
Done installing documentation for bundler after 2 seconds
1 gem installed
Resolving dependencies...
Fetching gem metadata from https://rails-assets.org/...
Fetching gem metadata from https://rubygems.org/.......
Your bundle is locked to mimemagic (0.3.0), but that version could not be found
in any of the sources listed in your Gemfile. If you haven't changed sources,
that means the author of mimemagic (0.3.0) has removed it. You'll need to update
your bundle to a version other than mimemagic (0.3.0) that hasn't been removed
in order to install.


STDERR:

+ export PATH=/home/leihs-legacy/.rubies/ruby-2.6.6/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
+ which gem
+ gem install bundler
+ cd /leihs/legacy
+ bundle install --retry=12 --without development --without test


MSG:

non-zero return code

Control and target machines are both running fresh installations of ubuntu 18.04 or debian 10.

Thanks in advance,
Matthias

How to run the commands to install Leihs on a Debian 10 server

Hello,

I'm trying to install it on a Debian 10 server but it doesn't work ...

I run commands 1, 2, 3, 4 and 6 on Debian 10 server but it doesn't work. Are these commands to be run on a Debian 10 system for example?
I run these commands in ssh via putty.

Thank you !

Deployment issues with Docker: SSH: mux_client_read_packet: read header failed: Broken pipe

Hello,

I hope somebody can help me with the following issues that appear during deployment via docker.
SSH connection can be established without any problems (key copied to server via ssh-copy-id)

Also I needed to pass-through ssh-key, to be able to install python (https://githubmemory.com/repo/leihs/leihs-instance/issues/8)

Thanks!

Host: OSX 10.15.7 / OpenSSH_8.1p1, LibreSSL 2.7.3
Server: Ubuntu 20.04.2 LTS /OpenSSH_8.2p1 Ubuntu-4ubuntu0.2, OpenSSL 1.1.1f 31 Mar 2020
Apache: 2.4.41
Docker: 3.5.1

task path: /leihs-instance/leihs/deploy/roles/leihs-legacy-install/tasks/install-ruby.yml:5
Using module file /usr/local/lib/python2.7/dist-packages/ansible/modules/command.py
Pipelining is enabled.
ESTABLISH SSH CONNECTION FOR USER: root
SSH: EXEC ssh -vvv -o ForwardAgent=yes -o ControlMaster=auto -o ControlPersist=60m -o StrictHostKeyChecking=no -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o 'User="root"' -o ConnectTimeout=10 -o ControlPath=/root/.ansible/cp/c958746181 mydomain '/bin/sh -c '"'"'sudo -H -S -n -u leihs-legacy /bin/sh -c '"'"'"'"'"'"'"'"'echo BECOME-SUCCESS-wpiqklcapmtyqltycxjkycxbcetmbhfr ; /usr/bin/python'"'"'"'"'"'"'"'"' && sleep 0'"'"''
Escalation succeeded
fatal: [mydomain]: UNREACHABLE! => {
"changed": false,
"unreachable": true
}

MSG:

Data could not be sent to remote host "mydomain". Make sure this host can be reached over ssh: OpenSSH_7.9p1 Debian-10+deb10u2, OpenSSL 1.1.1d 10 Sep 2019
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: auto-mux: Trying existing master
debug2: fd 3 setting O_NONBLOCK
debug2: mux_client_hello_exchange: master version 4
debug3: mux_client_forwards: request forwardings: 0 local, 0 remote
debug3: mux_client_request_session: entering
debug3: mux_client_request_alive: entering
debug3: mux_client_request_alive: done pid = 17
debug3: mux_client_request_session: session request sent
debug3: mux_client_read_packet: read header failed: Broken pipe
debug2: Control master terminated unexpectedly

PLAY RECAP *****************************************************************************************************************************************************************************************************************************
mydomain : ok=157 changed=47 unreachable=1 failed=0 skipped=28 rescued=0 ignored=0

Server ssh config:

#	$OpenBSD: sshd_config,v 1.103 2018/04/09 20:41:22 tj Exp $

# This is the sshd server system-wide configuration file.  See
# sshd_config(5) for more information.

# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented.  Uncommented options override the
# default value.

Include /etc/ssh/sshd_config.d/*.conf

#Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::

#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_ecdsa_key
#HostKey /etc/ssh/ssh_host_ed25519_key

# Ciphers and keying
#RekeyLimit default none

# Logging
#SyslogFacility AUTH
#LogLevel INFO

# Authentication:

#LoginGraceTime 2m
PermitRootLogin yes
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10

#PubkeyAuthentication yes

# Expect .ssh/authorized_keys2 to be disregarded by default in future.
#AuthorizedKeysFile	.ssh/authorized_keys .ssh/authorized_keys2

#AuthorizedPrincipalsFile none

#AuthorizedKeysCommand none
#AuthorizedKeysCommandUser nobody

# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes

# To disable tunneled clear text passwords, change to no here!
PasswordAuthentication yes
#PermitEmptyPasswords no

# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
ChallengeResponseAuthentication no

# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes
#GSSAPIStrictAcceptorCheck yes
#GSSAPIKeyExchange no

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication.  Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
UsePAM yes

#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
X11Forwarding yes
#X11DisplayOffset 10
#X11UseLocalhost yes
#PermitTTY yes
PrintMotd no
#PrintLastLog yes
#TCPKeepAlive yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS no
#PidFile /var/run/sshd.pid
#MaxStartups 10:30:100
#PermitTunnel no
#ChrootDirectory none
#VersionAddendum none

# no default banner path
#Banner none

# Allow client to pass locale environment variables
AcceptEnv LANG LC_*

# override default of no subsystems
Subsystem sftp	/usr/lib/openssh/sftp-server

# Example of overriding settings on a per-user basis
#Match User anoncvs
#	X11Forwarding no
#	AllowTcpForwarding no
#	PermitTTY no
#	ForceCommand cvs server

No customer Menu in top bar

Hello. I have installed an instance of leihs on an internal hosted server. It is working fine except for a little issue.:
When I log in as a "customer", the customer menu does not display and thus cannot log out?
Maybe I missed a configuration somewhere. Thanks Philipp
cust-menu-missing

docker deploy stuck at TASK [leihs-database-install : install ruby]

Just tried to install leihs on my server via docker and the TASK [leihs-database-install : install ruby] fails:

TASK [leihs-database-install : install ruby] **********************************************************************************************************************
fatal: [leihs-org-01...]: FAILED! => {}

MSG:

Failed to set permissions on the temporary files Ansible needs to create when becoming an unprivileged user (rc: 1, err: chown: changing ownership of '/var/tmp/ansible-tmp-1606172031.81-76742250625194/': Operation not permitted
chown: changing ownership of '/var/tmp/ansible-tmp-1606172031.81-76742250625194/AnsiballZ_command.py': Operation not permitted
chown: changing ownership of '/var/tmp/ansible-tmp-1606172031.81-76742250625194/async_wrapper.py': Operation not permitted
}). For information on working around this, see https://docs.ansible.com/ansible/become.html#becoming-an-unprivileged-user

I'm not sure how to fix it - so any help is appreciated.

Docker-Deploy stuck at TASK [install system python]

When I start the deploy from Docker script it always exits with Permission denied (publickey,password).

Here the full code where it exits:

PLAY [all] *****************************************

TASK [install system python] ***********************************
fatal: [IP]: UNREACHABLE! => {
    "changed": false, 
    "unreachable": true
}

MSG:

Failed to connect to the host via ssh: Warning: Permanently added 'IP' (ECDSA) to the list of known hosts.
root@IP: Permission denied (publickey,password).



PLAY RECAP *************************
IP            : ok=0    changed=0    unreachable=1    failed=0   

I've already checked if my SSH-Keys are correctly set up and that seems to be the case.

Update to 6.3.1

Hi,

How about to update leihs-instance master to 6.3.1.
thx

regards
Mario

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.