VM installs

And cjisble's instructions above worked for me for the embedded Linux terminal in the browser:

with changing the following in /etc/default/shellinabox:

cjisble wrote:

Interesting.  I didn't need to do this.  But if I check my machine, the frontail.service file does exist, with the contents described.

Perhaps this is because I used Ubuntu?

I don't see how a Ubuntu file could contain this: so I guess it got set up by myServer somehow.

bitzerjd wrote:

Notes, we don't need no stinking Notes.  Mid way through the process I thought, gee, I should really be writing this down.  From Memory... The Docker install (adding the repository) didn't work, I simply Googled install Docker on Debian 12 and followed the instructions.  Python Dev didn't install, the installer recommended a different version.  Pyatv required me to go to their website for instructions.  Visudo didn't like the suggested change.  Again, I googled how to do it, and it gave me a format that worked.  Finally the swap file add to fstab was a bit unclear, I modified mine and I didn't boot back up.  I need to modify it today.

Here is another example...at the end it says to run this "sudo cat /home/allonis/myServer/logs/myServer.log".  The problem is that it fails because it left out the "applications" directory.  It should say sudo cat /home/allonis/applications/myServer/logs/myServer.log.

My current issue is that the Live Log viewer doesn't connect.  The log is populated so I'm thinking it is a port issue (9001).  I need to work on it this morning.   Hmmm, also the Linux Terminal from the main web page doesn't work.  I think the log viewer and this issue is related.  Unfortunately, my Linux skills are at a hack and slash level.
 

I did make notes, but I'm not sure if anyone other than me can understand them.

As far as Linux skills go, I just slash, so you already know twice as much as I do.

The nice thing about virtual machines is that it is easy to backup before you try something and start over when you have to.
 

andrew wrote:

cjisble wrote:

Interesting.  I didn't need to do this.  But if I check my machine, the frontail.service file does exist, with the contents described.

Perhaps this is because I used Ubuntu?

I don't see how a Ubuntu file could contain this:

Code:

ExecStart=frontail --ui-highlight --disable-usage-stats /home/allonis/applications/myServer/logs/myServer.log

so I guess it got set up by myServer somehow.
 

Yes.  The file is located in applications/myServer/data/linux.x64.

The instructions said to copy the files from there into lib/systemd/system.

I copied all three service files, not just myServer.service and myInstaller.service.

 

cjisble wrote:

andrew wrote:

cjisble wrote:

Interesting.  I didn't need to do this.  But if I check my machine, the frontail.service file does exist, with the contents described.

Perhaps this is because I used Ubuntu?

I don't see how a Ubuntu file could contain this:

Code:

ExecStart=frontail --ui-highlight --disable-usage-stats /home/allonis/applications/myServer/logs/myServer.log

so I guess it got set up by myServer somehow.


 

Yes.  The file is located in applications/myServer/data/linux.x64.

The instructions said to copy the files from there into lib/systemd/system.

I copied all three service files, not just myServer.service and myInstaller.service.



 

Which instructions? I was following  allonis.com/support/documentation?view=category&id=416 and don't see that there - those instructions get you to create myServer.service and myInstaller.service by editing them.

Actually now I see you have at the end of your forum post "8.  Copy the myServer files and start the Services" but I don't see that in the 'official' instructions I was looking at.

Reviewing my notes, I found a couple of other things I did that were not in the instructions.

I installed the package WSDD, which makes a Samba Host discoverable by Windows clients.  This allows the VM to appear under Network, and the shares are browsable.

I used timedatectl to set the timezone, so the timestamps in the log would be meaningful.

The nVidia Shield runs Android 9.1.  to connect to the Shield via ADB, you must be using at least version 30 of ADB.  The package manager downloaded version 28.  I went to developer.android.com and downloaded the platform-tools.  I then copied the adb file to the server, and updated the permissions.  This probably completely screws up the package manager, but I couldn't find any other way to do it.