mv: cannot stat '/var/log/syslog': No such file or directory

[Alberto Quijada]

Hi there,

I've just installed a BBB 0.90 in Ubuntu 14.04.2 LTS, following the instructions at http://docs.bigbluebutton.org/install/install.html

Every step has worked well, but at the 9th one, while running: 'sudo bbb-conf --clean', I've got this:

...

Cleaning Log Files ...

mv: cannot stat ‘/var/log/syslog’: No such file or directory

...

I've reading about the script *bbb-conf*, finding these lines:

...

rm -rf /var/log/nginx/*

mv /var/log/syslog /tmp/syslog.$$

echo "" > /var/log/syslog

chown syslog:adm /var/log/syslog

...

Where it's clear that the error takes place.

The point is that this Ubuntu 14.04.2 LTS comes from a Puppet template, as there are some personal configurations shared by the servers in my organization. One of them is that our syslog is configured in order to save messages at /var/log/messages. Understanding that the system programmer doesn't need to know about which file is used to save the messages, as there are system calls so as to communicate with syslog, then I don't really agree with this way of doing things, I mean, using the literal '/var/log/syslog'.

Notice that the rest of messages showed by this command are all OK, and the BBB Server seems to work perfectly.

But I would like to know how important is really this issue in order to go ahead.

By the way, I would like to know if there is some documentation about making a Puppet template for a complete working BBB Server, as it's my next goal. I'll be pleased to share it as soon as I get it :-)

Many thanks in advace.

Regards.

[Fred Dixon]

Hi Alberto,

> mv /var/log/syslog /tmp/syslog.$$

> echo "" > /var/log/syslog

> chown syslog:adm /var/log/syslog

You can comment these lines in /usr/bin/bbb-conf without any side effect.  The purpose of these lines was when you did 

  sudo bbb-conf --clean

the restart would "clean" out all the BigBlueButton log files so that later, if you did

  sudo bbb-conf --debug

which searched log files for potential errors thrown by BigBlueButton, the grep commands would not file errors in the log files before the restart.

We used this for testing BigBlueButton when we found an issue with BigBlueButton that put an error in the log.  We would apply a fix, then do "sudo bbb-conf --clean" and repeat the steps to see if the issue (and corresponding log message) was fixed.

> By the way, I would like to know if there is some documentation about making a 

> Puppet template for a complete working BBB Server, as it's my next goal. I'll be 

> pleased to share it as soon as I get it :-)

Please do.  The steps at 

   http://docs.bigbluebutton.org/install/install.html

are pretty straightforward and could be turned into a Puppet/Chef/Ansible script.  

Regards,... Fred

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-Setup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-s...@googlegroups.com.
To post to this group, send email to bigbluebu...@googlegroups.com.
Visit this group at http://groups.google.com/group/bigbluebutton-setup.
For more options, visit https://groups.google.com/d/optout.

--

BigBlueButton Developer

http://bigbluebutton.org/
http://code.google.com/p/bigbluebutton

BigBlueButton on twitter: @bigbluebutton