Hi,
you can disregard those warnings.
Thanks reporting them, though. We'll try and fix it for future packages.
cheers,
Jaime
On Mon, Jan 14, 2013 at 3:32 PM, Andreas Calvo Gómez <
andreas.ca...@scytl.com> wrote:
> We will try it under our maintenance schedule.
>
> However, stopping and star
We will try it under our maintenance schedule.
However, stopping and starting daemons shows the following warnings:
[root@opennebula ~]# /etc/init.d/opennebula-occi stop &&
/etc/init.d/opennebula-sunstone stop && /etc/init.d/opennebula stop &&
/etc/init.d/httpd stop
Stopping OCCI Server daemon
Hi,
I guess you are referring to the old documentation, right? I found the
warning about sqlite and NFS in the 3.2 archives [1]. It should be enough
if you move the one.db file and create a symlink.
Regards
[1]
http://opennebula.org/documentation:archives:rel3.2:sfs#considerations_limitations
--
Carlos,
We are exporting the whole /var/lib/one directory as per the
documentation, which helps to maintain all the cloud by sharing the same
ssh public keys and configuration.
Do you think placing the SQLite database in a non-NFS directory will
make things better?
On 11/01/13 14:09, Carlos
Hi,
Are you exporting only the shared datastores, or the whole /var/lib/one
location?
In older versions we advised to share /var/lib/one to make the ssh
configuration easier, but NFS would make the sqlite DB misbehave.
Regards
--
Carlos Martín, MSc
Project Engineer
OpenNebula - The Open-source So
Hello,
We've been using ONE for some time now, and it worked flawlessly.
A month ago, we switched from GFS to NFS to shared storage, because GFS
is really difficult to maintain and operate.
We found out that Sunstone is becoming inactive randomly: while the
WEBUI seems to be working, users ca
