Open marfrit opened 6 years ago
@marfrit apologies for the delayed response.. You're right, 16.04 symlinks /var/run
to /run
:
$ ls -la /var/run
lrwxrwxrwx 1 root root 4 Jul 27 08:28 /var/run -> /run
And in your case, you're out of room in /run
. As a workaround, you could move zeppelins webapps someplace else (/var/lib/zeppelin
seems appropriate):
$ juju ssh zeppelin/0
...
ubuntu@ip-172-31-6-139:~$ cd /etc/zeppelin/conf
ubuntu@ip-172-31-6-139:/etc/zeppelin/conf$ sudo cp zeppelin-env.sh zeppelin-env.sh.orig
## sudo vi zeppelin-env.sh
ubuntu@ip-172-31-6-139:/etc/zeppelin/conf$ diff -u zeppelin-env.sh.orig zeppelin-env.sh
--- zeppelin-env.sh.orig 2018-08-06 15:56:36.802403316 +0000
+++ zeppelin-env.sh 2018-08-06 15:52:58.308325812 +0000
@@ -18,7 +18,7 @@
export ZEPPELIN_CONF_DIR=/etc/zeppelin/conf
export ZEPPELIN_LOG_DIR=/var/log/zeppelin
export ZEPPELIN_PID_DIR=/var/run/zeppelin
-export ZEPPELIN_WAR_TEMPDIR=/var/run/zeppelin/webapps
+export ZEPPELIN_WAR_TEMPDIR=/var/lib/zeppelin/webapps
export ZEPPELIN_NOTEBOOK_DIR=/var/lib/zeppelin/notebook
export MASTER=local[*]
export SPARK_HOME=/usr/lib/spark
ubuntu@ip-172-31-6-139:/etc/zeppelin/conf$ exit
...
$ juju run-action --wait zeppelin/0 restart
unit-zeppelin-0:
id: 3af66652-d463-486c-8842-30a2321c2752
status: completed
timing:
completed: 2018-08-06 15:57:04 +0000 UTC
enqueued: 2018-08-06 15:56:55 +0000 UTC
started: 2018-08-06 15:56:56 +0000 UTC
unit: zeppelin/0
Bigtop does allow the war tmpdir to be declared at install time, but the zeppelin charm does not expose this as a config option.
I'll leave this open as a feature request, but hopefully the above workaround gets you unblocked.
I just created a zeppelin installation using "juju deploy zeppelin". Here's where I got stuck (the installation is created using a KVM based virtual machine managed by a MAAS pod):
From /var/log/zeppelin/zeppelin-zeppelin-v010203.log:
I looks to me that the default zeppelin directory defaults to /run which is created with a (small) size in Ubuntu 16.04 (nowadays?).