The goal of this document is to provide a list of Frequently Asked Questions, and their answers.
A: Follow the official documentation at http://community.slapos.org.
A: VIFIB has been renamed slapos.org quite recently. You can find "vifib" written sometimes in the SlapOS Node, but it means "slapos.org".
To create a slapos.org account, just go to slapos.org, click "login" then "join".
A: go to "My Space", "My Servers", click on your Node, then "Update Allocation
Scope", then change it to read "Closed / Closed forever".
A: Just destroy your current service on SlapOS Master, then request a new one.
A: Read the different examples available in the end of http://git.erp5.org/gitweb/slapos.git/blob/HEAD:/software/apache-frontend/README.apache_frontend.txt?js=1#l121 .
Note that you should have a configured SlapOS Client. Click here for the tutorial : http://community.slapos.org/wiki/osoe-Lecture.SlapOS.Extended/developer-Installing.SlapOS.Client. Your client slapos.cfg should be up to date compared to http://git.erp5.org/gitweb/slapos.core.git/blob/HEAD:/slapos-client.cfg.example.
A: Follow this link to read the answer: http://www.slapos.org/wiki/slapos-Contribute.Buildout
A: Thanks for reporting this lurking bug on the SlapOS forum, we'll take care of it.
A: You can run two commands that are run automatically, just to be sure that they don't throw any error:
# slapos node format --now -v
# slapos node instance
A: If, when running slapgrid, you have an error like this one:
It means that the server dropped the connection. It is likely that if you try again after a few seconds, it will work correctly.
A: This error is like:
socket.error: Couldn't connect to the server. Please double check given master-url argument, and make sure that IPv6 is enabled on your machine and that the server is available. The original error was:_ssl.c:488: The handshake operation timed out
It means that SlapOS failed to correctly connect to the server. To understand the problem, you need to read the last part of the error.
Here it is "The handshake operation timed out". It means that the server was to slow/busy to answer. Just try again in a few minutes.
Couldn't authenticate computer. Please check that certificate and key exist and are valid. [Errno 336265225] _ssl.c:351: error:140B0009:SSL routines:SSL_CTX_use_PrivateKey_file:PEM lib
It means that the SlapOS Node could not authenticate itself to the server. To know what is happening, you should read the last part of the error.
A: When you are online again, with IPv6 connectivity, you just should run slapgrid (or let it be run again by cron). It should continue its work if any.
If your network configuration is complex, you should check if it corresponds to tutorials pages (is the bridge okay?).
A: Error is like:
Error: The directory:
to be used as a download cache doesn't exist.
Make sure that the tmp directory is accessible to the "slapsoft" user.
Particularly, we've seen configurations where $TMPDIR was set to /root/tmp. Here, obviously, /root is not accessible to the "slapsoft" user, so buildout, run as slapsoft, miserably failed to create a directory there.
1/ Let's say we have a SlapOS Node with a Software Release http://mywebsite.com/my-software/software.cfg installed, and a deployed instance named "my instance" of it.
2/ Then, the Software Release http://mywebsite.com/my-software-v2/software.cfg is released, let's say for an important security fix.
The question is: how to upgrade my existing instance to the new Software Release to benefit the security fixes?
Install (= supply) the new Software Release in the machine (here, http://mywebsite.com/my-software-v2/software.cfg)
Tell SlapOS to change your existing instance from the old Software Release to the new Software Release. It is currently only possible from the command line, configured with your account (see documentation to configure it):
slapos request "my instance" http://mywebsite.com/my-new-software/software.cfg
Then, slapos will change the links in "my instance" from the old Software Release to the new one.
Beware : currently, the new Software Release has to be backward compatible with the old one.
A: This is a known bug of the beta version of SlapOS. It is solved in SlapOS 1.0.
A: This is a known issue and you should be able to reconnect after sometime.
A: It's a mysql/mariadb bug reported at http://bugs.mysql.com/bug.php?id=61575 On the dedicated USB key, we solve it like this: http://git.erp5.org/gitweb/slapos.package.git/commit/43f91454faad7d6cd82ada8300ec4aebc983219c?js=1 Our fix is based on http://johanlouwers.blogspot.fr/2010/02/aio-max-nr-parameter-for-oracle.htm
A: A possible source of problem is that the IPv4 of MariabDB changed. This bug is not yet well understood. You can compare, in /opt/slapos directory, your slapos.xml with backups in slapos.xml.zip, and if needed, replace slapos.xml by one of its backup, then reboot.