Please upgrade to build #3263 and then reinstall agent to see if it works.

Note that agent needs to be re-downloaded from server.

i upgrade to 7.9.2 and reinstall agent from link provided by server.

Still not working as service, the executable ends with "see logs/console.log" which not exists.

What your Mac cpu arch?

Also please download JSW test package: https://download.tanukisoftware.com/wrapper/3.5.51/wrapper-delta-pack-3.5.51-st.tar.gz

Extract it, change to bin directory, edit testwrapper to uncomment RUN_AS_USER, and specify a user, then run ./testwrapper install to see what happens (you may run ./testwrapper remove to uninstall it)

Intel Core i7 Core architecture. We've also test on M1 Arm64 and still not working.

After adding our user RUN_AS_USER=one-dev to testwrapper :

1. ./testwrapper console [OK]
2. sudo ./testwrapper install [OK]
3. sudo ./testwrapper start [ERROR] same as above except the log file is created but always empty.

I tested both on my Mac (Intel cpu, Ventura 13.1), and a fresh started Mac2 instance on AWS (arm cpu, Ventura 13.1), and OneDev agent can be installed as service and started without any issues.

Please make sure you've specified path to java executable via property "wrapper.java.command" in "conf/wrapper.conf" if root user can not find java in its path

The wrapper.java.command seems correct and we test with the fullpath java value. Still not working.

BUT

All console tests we did before was with user role.

• ./agent.sh console [OK]
• sudo ./agent.sh console [ERROR] crash in few seconds

So it seems the issue come from the root env.

We enabled debug log in the wrapper.conf and the run the console.

You can see log attached with a NPE : console.log and agent.log

Agent running as service trying to clean temp directory ends by a NPE ?

maybe a issue in right management as service run by root do not access to the user directory even with the correct RUN_AS_USER in the agent.sh ?

This is a permission issue. Please make sure the RUN_AS_USER owns the agent install dir and all content under it recursively.

Closing. Feel free to reopen if there are more issues.

We tried on a fresh MacOS X.

• install jdk 19
• install git
• download onedev agent
• set RUN_AS_USER variable

same : ./agent.sh console working but sudo ./agent.sh start failed

Robin, could you provide your steps ?

Maybe we are doing something wrong but quite frankly we don't know what...

The only difference might be JDK. I installed jdk using brew and guess it is not JDK 19. OneDev only supports up to JDK 17 LTS version.

Also does the RUN_AS_USER owns the agent directory and everything underneath it?

OpenJDK17 installed with brew.

We can reproduce.

• agent console [OK]
• agent install && agent start [ERROR]
• agent start (only) [OK]

see screenshoot

we can give you ssh access for this macos test.

Yes, please give me ssh access and I will check it tomorrow. I've made this issue confidential so that others can not see sensitive info.

Thanks.

My coworker is preparing the macosx. Once done we'll send you credencials and you'll able to connect when you want

OK, will test it later today.

Found the problem. When files are extracted to Downloads or Desktop (may also include some other Mac managed folders), Mac sets extended attributes ('@' in permission bits of some file when you run ls -l <agent dir>/bin), which prevents the agent process from writing into it.

To solve the issue, just extract agent package into a different folder, for instance, /Users/macbuildsession/agent. If you copy existing agent directory from Desktop to some other place, you will need to run sudo xattr -cr ./agent to remove extended attributes.

I removed login information, and will make the issue public again.

I will also add a note in agent installation guide for this.

That was very vicious... THANKS Robin !!