Arch Linux User Repository

Some pretty significant changes recently, so read carefully and don't be afraid to comment asking for clarification or offering suggestions. As of version 20.11.2-2 this package switches to using upstream's systemd service files instead of separate downstream versions. The new service files assume a different data directory path and use of a dgraph user, both of which are typically set up via upstream's add_dgraph_account.sh script. This script has been wrapped with the dgraph-bin.install file in this package to handle different cases, such as updating from the old service files to the new service files. The upstream dgraph-alpha service automatically starts the dgraph-zero service, so starting them both when they are initially down is as simple as systemctl start dgraph-alpha.

Additionally, upstream is moving away from including ratel releases with dgraph releases since ratel has now been open sourced in its own separate repository. As such, versions 21.03.0-1 and onwards of this package do not contain the dgraph-ratel binary and dgraph-ui.service file. Instead, they have been moved to a separate package which uses the upstream ratel releases. Note that the dgraph-ui service is not dependent on the other two, so you must specify the dgraph-alpha service if you wish to start all three services (systemctl start dgraph-alpha dgraph-ui).

Finally, version 21.03.0 marks the start of a new release series and thus contains breaking changes. When upgrading, please make sure to follow the dgraph documentation's recommendations; in particular, you should follow either the backup/restore or export/import process to transfer your data between major versions.

As of March 2020, dgraph has switched from semantic versioning to calendar versioning. Upstream will start a new release series every 4 months, and a release series will be supported for 12 months (security patches 18 months). As can be seen in the git log, I experimented with providing PKGBUILDs for the latest release in all currently supported series. I had hoped that the AUR server would rely on $pkgver in the PKGBUILD when offering the latest release, but it instead uses the latest commit. This will break new installations and upgrades of existing installations for any release series except the most recent release. Moving forward, I will only provide releases for the most recently created release series (i.e. 20.07 at this time until 20.11 is released and so on). This is in line with the Arch Linux Principles. If you wish to get a different version than the latest, download the PKGBUILD, change $pkgver, and proceed with building the package as normal. You can also follow the standard downgrade guidelines provided in the wiki.

Running makepkg -si I get a FAILED VALIDITY CHECK for dgraph-zero.service.

Had to update PKGBUILD with following 256 hash:

$ sha256sum dgraph-zero.service
1d717b444a2bd4a6a5bfe035c8e46bba8319793f9ca211c3d815fa24327dc37f dgraph-zero.service

I haven't had time to maintain this package, so I just disowned it. I'm realizing it might've been smoother of a process to add @tee before doing that, but I didn't think of that before pushing the button, sorry! Assuming you're interested in maintaining, you should get a request approved by the trusted users at some point.

Any plans on updating this package?

Hi @bruno.unna , thanks for finding and posting the relevant portions from the logs. The NODE_MODULE_VERSION error seems to indicate that something needs rebuilt every time the ABI version gets bumped. The Running node command error text comes from this file, which suggests you are using dgraph-lambda.

Can you confirm if you have dgraph-lambda installed and if so, if rebuilding that fixes the issue?

If not, does switching from dgraph-bin to dgraph-git (which would cause a rebuild of dgraph) fix the issue?

Newbie here.

This is the first problem I saw in the logs, repeatedly (every two seconds):

May 30 12:00:41 singularity bash[16609]: I0530 12:00:41.799551   16631 run.go:533] Running node command: node t/index.js
May 30 12:00:41 singularity bash[16609]: E0530 12:00:41.799608   16631 run.go:535] Failed to start lambda server at port: 20000. Got err: exec: "node": executable file not found in $PATH

I reckoned this was due to node not being installed in my system. So I installed it and then I started receiving this one:

May 30 12:38:12 singularity bash[27077]: I0530 12:38:12.104053   27097 run.go:533] Running node command: /usr/bin/node t/index.js
May 30 12:38:12 singularity bash[27077]: /var/lib/dgraph/t/index.js:2
May 30 12:38:12 singularity bash[27077]: [47.9K blob data]
May 30 12:38:12 singularity bash[27077]: n e}}))),a}S.status=function(e){return this.statusCode=e,this},S.links=function(e){var t=this.get("Link")||"";return t&&(t+=", "),this.set("Link",t+Object.keys(e).map((function(t){return"<"+e[t]+'>; rel="'+t+'"'})).join(", "))},S.se>
May 30 12:38:12 singularity bash[27077]: Node.js v18.2.0
May 30 12:38:12 singularity bash[27077]: E0530 12:38:12.265883   27097 run.go:543] Lambda server at port: 20000 stopped with error: exit status 1

I kept watching the logs, and found this:

May 30 12:38:32 singularity bash[27077]: Error: node-loader:
May 30 12:38:32 singularity bash[27077]: Error: The module '/var/lib/dgraph/t/238e74e906bbea8f81bc0ffc69ff2e86.node'
May 30 12:38:32 singularity bash[27077]: was compiled against a different Node.js version using
May 30 12:38:32 singularity bash[27077]: NODE_MODULE_VERSION 83. This version of Node.js requires
May 30 12:38:32 singularity bash[27077]: NODE_MODULE_VERSION 108. Please try re-compiling or re-installing
May 30 12:38:32 singularity bash[27077]: the module (for instance, using `npm rebuild` or `npm install`).

At this point I've run out of ideas, I'm afraid (not an expert on node.js).

My system: ArchLinux updated today. Kernel: 5.18.0-zen1-1-zen Nodejs: 18.2.0-1

Any help will be appreciated.

Thanks!!!

You're welcome and thanks for the feedback! Your observation is correct, so I updated my pinned comment accordingly.

a

Some pretty significant changes recently, so read carefully and don't be afraid to comment asking for clarification or offering suggestions. As of version 20.11.2-2 this package switches to using upstream's systemd service files instead of separate downstream versions. The new service files assume a different data directory path and use of a dgraph user, both of which are typically set up via upstream's add_dgraph_account.sh script. This script has been wrapped with the dgraph-bin.install file in this package to handle different cases, such as updating from the old service files to the new service files. The upstream dgraph-alpha service automatically starts the dgraph-zero service, so starting them both when they are initially down is as simple as systemctl start dgraph-alpha.

Additionally, upstream is moving away from including ratel releases with dgraph releases since ratel has now been open sourced in its own separate repository. As such, versions 21.03.0-1 and onwards of this package do not contain the dgraph-ratel binary and dgraph-ui.service file. Instead, they have been moved to a separate package which uses the upstream ratel releases. Note that the dgraph-ui service is not dependent on the other two, so you must specify the dgraph-alpha service if you wish to start all three services (systemctl start dgraph-alpha dgraph-ui).

Finally, version 21.03.0 marks the start of a new release series and thus contains breaking changes. When upgrading, please make sure to follow the dgraph documentation's recommendations; in particular, you should follow either the backup/restore or export/import process to transfer your data between major versions.

@galaux thanks for pointing that out, I plan to switch when I return to a non-metered internet connection soon. The upstream-provided files look rational at a glance, though I'll test what the transition to a dgraph system user is like before I push anything.