Jamulus
A problem following instructions installing server 3.7.0 #1322
Replies: 3 comments 11 replies
-
|
Now that the recommended method of setting up a headless server is with the binary install, we will be moving the manual installation instructions into a separate file in the repo. So with luck some of your questions won't come up, since things like paths and whatnot are all pre-determined. However, in common with most projects, Jamulus also has a problem when presenting documents like the one you are reading: what level of assumed knowledge should we cater for? For example "how to check that the command completed properly" is something that is common to any service being managed by systemd (you use systemctl or journalctl). Should we explain that? (I think we do in fact? See the section headed "Test that it starts OK"). Uncharitably, there are some who are of the opinion that if you don't know how to install a systemd service on Linux then you shouldn't be running a headless server (since there are security and other issues to take care of as well). I'm not of that opinion, but it's a tough one. |
Beta Was this translation helpful? Give feedback.
-
|
But to answer your questions meanwhile:
No.
Assuming you are using
It's doesn't unless you mean a lockfile.
Good point, although I'm not sure how many actually generate defaults. As to examples I would hope the options table is fairly simple in that regard. Did you have any specific examples in mind?
This isn't expected. I can't reproduce it at my end. It seems to indicate the unit file wasn't created though. Might need to look at this as it may be a bug? |
Beta Was this translation helpful? Give feedback.
-
|
@gilgongo Thank you for your reply. I'll respond to each issue here.
I propose Jamulus is for a computer literate musician. We shouldn't require the musician to be a software developer or a highly experienced Linux admin.
To be explicit, we should say, after this step, the file jamulus-headless.service will appear in ddd directory. We need to specify the files that are created? This way, the user can confirm nothing is missing and there are no surprises. In my example, we don't have a clue that step 3 completed correctly and we don't know why step 4 will not run.
It is the culture of some developers to create solutions or themselves or only people expert like them. Jamulus is a wonderful tool for musicians. Most musicians are not developers. One choice is to say, Jamulus is not an end user product and musicians who are not developers should use a commercial Jamulus service. I hope this is not a serious choice. Let's make get even novice users to be successful installing a server. Security and other issues is a lesson for another day. The documentation could say, security and other issues should be part of a complete installation. It would be then the assignment for the user to research.
From my experience with server 3.6.3, this will fail because jamulus-headless.service is missing. But that is a novice's guess.
I was being too vague. In this example, step 3 should have created jamulus-headless.service in some directory. Where? What other files were touched or created? We should tell the user how to confirm the command (e.g. step 3) was properly done.
A bug? Oh no! Does this mean I can't install 3.7.0? Because of the changes in the repository, my 3.6.2 install scripts are also broken. I'll have to figure out how to update these scripts (written by a friend). Sadly I don't have a method to revert back to a working image. |
Beta Was this translation helpful? Give feedback.
-
|
Does /lib/systemd/system/jamulus-headless.service exist and can you run Also: have a look at the syslog ( |
Beta Was this translation helpful? Give feedback.
-
I agree. But please consider that you don't also don't need to run a server (let alone a headless one on Linux) to use Jamulus. That's entirely optional.
OK, but this would assume that if the user doesn't know how systemd works, then we need to explain all the attendant concepts to that as well, since systemd expects /lib/systemd/system/ is where all such unit files live by convention.
In Unix, commands tend to complete silently if they are successful, again by convention. We could put a message in the installer, but no other installers do that to my knowledge. BTW if you are on Debian or Ubuntu, you can run
Beyond a general statement, specifics would be entirely dependent on what security environment they have, and there are too many variations of this. |
Beta Was this translation helpful? Give feedback.
-
|
@gilgongo propably I used the wrong Jekyll variable there. Can you change it on release for all languages? |
Beta Was this translation helpful? Give feedback.
-
|
Progress report: 1 Download 3- Install the package 4- Enable the headless server..... Thanks for clues. |
Beta Was this translation helpful? Give feedback.
-
|
Ok. Maybe once you set it up, you can open a Pull Request to the changes branch for changing the process to a more user friendly way |
Beta Was this translation helpful? Give feedback.
-
At the risk of me appearing silly, you don't literally mean a path called "/path/to" do you? That's just for purposes of the docs, we're not expecting you to actually create it. Some install guides say you should cd to /tmp though, which may be clearer? |
Beta Was this translation helpful? Give feedback.
-
|
Well, I originally thought it couldn't have been literally /path/to. BUT after your comments, I moved to path/to/jamulus_headless_3.7.0_ubuntu_amd64.deb AND step 3 and step 4 worked. So both you and I were wrong to think it was silly. Maybe we want to change the location? /etc/jamulus/jamulus_headless_3.7.0_ubuntu_amd64.deb? |
Beta Was this translation helpful? Give feedback.
-
|
Is there something illformed with this ExecStart from my jamulus-headless.service?
Not all the parameters are seen in systemctl status jamulus-headless. Does the status look right? The server is not registering with the directory (or the directory server is not showing this server).
|
Beta Was this translation helpful? Give feedback.
-
I am following the instructions at jamulus.io/wiki/Server-Linux Running a "headless" server.
At step 3, it would be helpful to know (1) does it matter which directory the command should be run, and (2) what is the result of the command, or how to check that the command completed properly. It could be, the command will create a file ffff in directory dddd.
Running step 4, I get the error "Failed to enable unit: Unit file jamulus-headless.service does not exist."
From which directory should this command be issued? I haven't been able to guess where jamulus-headless.service should be found. I'm stuck.
Looking ahead at step 5, I have experience with some command line options for 3.6.2. However, it would be helpful for new server installers to have some command line examples. The options table could also use an explicit mention of the defaults if an option is not selected.
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions