[gotify] requires GLIBC_2.28

[SalocinHB]

… but CentOS 7 only provides up to GLIBC_2.17

[franok]

+1

since gotify server version 2.1.7

@SalocinHB will you be able to provide GLIBC_2.28 (or higher) on uberspace7?

[eitch]

I had a the same issue, thankfully i could build it on the space itself, so i can now run gotify 2.2.0

[noave]

will you be able to provide GLIBC_2.28 (or higher) on uberspace7?

sadly no @franok because this deeply linked to the OS, there unfortunately wont be a higher GLIBC on U7, but of course in following products

[noave]

thankfully i could build it on the space itself, so i can now run gotify 2.2.0 can you provide a solution for this in the guide @eitch ?

[eitch]

I basically followed the steps required here: https://gotify.net/docs/dev-setup

# ssh into box, then execute the following commands

# first install gotify:
mkdir ~/gotify && cd ~/gotify
wget https://github.com/gotify/server/releases/latest/download/gotify-linux-amd64.zip
unzip gotify-linux-amd64.zip
wget -O config.yml https://raw.githubusercontent.com/gotify/server/master/config.example.yml
vi ~/etc/services.d/gotify.ini

# now build gotify
git clone https://github.com/gotify/server.git
cd server
git checkout v2.2.2
make download-tools
go get -d
cd ui
yarn
yarn build
cd ..
go run hack/packr/packr.go
export LD_FLAGS="-w -s -X main.Version=$(git describe --tags | cut -c 2-) -X main.BuildDate=$(date "+%F-%T") -X main.Commit=$(git rev-parse --verify HEAD) -X main.Mode=prod";
# don't run as it requires docker: make build-linux-amd64
# just run:
go build -ldflags="$LD_FLAGS" -o gotify-server
# replace previous binary:
mv gotify-server ../gotify-linux-amd64

I've sent in a PR for the doc: https://github.com/Uberspace/lab/pull/1463

[eitch]

I just tested an upgrade to 2.2.2, this worked for me, by just executing all the commands again, and restarting the gotify service.

[franok]

can the mentioned PR to update the guide be merged?

[eitch]

Good question. I haven't heard back yet on my PR

[SaschaMann]

The same applies to focalboard when installed according to the guide.

2024-09-30 10:18:02,010 DEBG 'focalboard' stderr output:
/home/[...]/focalboard/bin/focalboard-server: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /home/[...]/focalboard/bin/focalboard-server)

2024-09-30 10:18:02,011 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 139755261106440 for <Subprocess at 139755259969808 with name focalboard in state STARTING> (stderr)>
2024-09-30 10:18:02,011 DEBG fd 7 closed, stopped monitoring <POutputDispatcher at 139755261106656 for <Subprocess at 139755259969808 with name focalboard in state STARTING> (stdout)>
2024-09-30 10:18:02,012 INFO exited: focalboard (exit status 1; not expected)
2024-09-30 10:18:02,012 DEBG received SIGCLD indicating a child quit
2024-09-30 10:18:02,013 INFO gave up: focalboard entered FATAL state, too many start retries too quickly