Where can I find the log files of hifi on Ubuntu?


I haven’t found them until now.


Depends the method you used to compile/run it.

My script does not write log files any more as it was eating up major amounts of space on the drive.

Other methods it depends on how you executed it.


Thanks @Coal, maybe you have a hint more for me?

I compile it at a VPS with
cmake …/hifi/ -DQT_CMAKE_PREFIX_PATH=/usr/local/opt/qt/5.4.1/lib/cmake
make assignment-client
make domain-server

I start it with:
screen -S stack -d -m ./domain-server
screen -S assign -d -m ./assignment-client -n 4


@summer4me… they are located in /var/log

To start you can try:
cd domain-server
./domain-server (which you have already)
cd assignment-client
./assignment-client -n 4 (which you have as well)

This is probably the same thing as you are trying however make sure that when you:
git pull (from the hifi directory) - you reboot directly after and then CD into the build folder and cmake …


Thanks @KevinMThomas, well I also have thought, that I would find them in var/log, but there I haven’t found log files from the assignment-client or domain-server, how they were written from the stack manager at my Mac.

And yes, the full start script is :
cd compile
cd domain-server
screen -S stack -d -m ./domain-server
cd …
cd assignment-client
screen -S assign -d -m ./assignment-client -n 4

But why I should reboot the server after git pull?
My compile script is:
git clone https://github.com/highfidelity/hifi.git
mkdir compile
cd compile
cmake …/hifi/ -DQT_CMAKE_PREFIX_PATH=/usr/local/opt/Qt5.4.1/5.4/gcc_64/lib/cmake/
make assignment-client
make domain-server

Until now this has worked.


You can run your domain server like this:
./domain-server &> domain.log&

It will write to domain.log in the same directory as the domain server
You can use tail -f domain.logto follow the log as it is written as well.

I prefer to use nohup rather than screen. Here is what my startup file looks like:
nohup ./domain-server &> domain.log&
nohup ./assignment-client -t 0 &> ac0.log&
nohup ./assignment-client -t 1 &> ac1.log&
nohup ./assignment-client -t 6 &> ac6.log&

I run assignment clients one node at a time (rather than using -n 4, which means 4 nodes will run) because some of us have noted there are less problems that way.


Thanks @Cracker_Hax, will try it, if I update next time my server.
Until now MagicGame was stable with the screen method. So I have not searched before for the log files.
I only have seen, that the log files of my localhost at the Mac were grown to some Gigabytes over the time and so I now also have searched at the server for the log files.
Dos it mean, that

screen -S stack -d -m ./domain-server
screen -S assign -d -m ./assignment-client -n 4

don’t write log files? This is, what I want in the moment.


I couldn’t find my log files when I used that method either.