I have my "server" running on 2.x now. I found the elasticsearch upgrade
info helpful, and it pretty much just worked. Graylog was another matter.
It took me most of the day to get it working again, and I still have a few
issues.
1) The el6 init.d script didn't work for me without replacing several of
the variables with the actual entries. This defeats the purpose of using
variables
path.env, path.conf and stopping.timeout threw errors. Didn't matter if
they were defined in server.conf or not.
The "-E" run arguments are supposed to be "-D" run arguments.
# Sets the default values for elasticsearch variables used in this script
ES_USER="elasticsearch"
ES_GROUP="elasticsearch"
ES_HOME="/usr/share/elasticsearch"
MAX_OPEN_FILES=65536
MAX_MAP_COUNT=262144
LOG_DIR="/var/log/elasticsearch"
DATA_DIR="/var/lib/elasticsearch"
CONF_DIR="${path.conf}"
PID_DIR="/var/run/elasticsearch"
# Source the default env file
ES_ENV_FILE="${path.env}"
if [ -f "$ES_ENV_FILE" ]; then
. "$ES_ENV_FILE"
fi
# CONF_FILE setting was removed
if [ ! -z "$CONF_FILE" ]; then
echo "CONF_FILE setting is no longer supported. elasticsearch.yml must
be placed in the config directory and cannot be renamed."
exit 1
fi
<clip>
start() {
<clip>
cd $ES_HOME
echo -n $"Starting $prog: "
# if not running, start it up here, usually something like "daemon
$exec"
daemon --user $ES_USER --pidfile $pidfile $exec -p $pidfile -d
-Ees.default.path.home=$ES_HOME -Ees.default.path.logs=$LOG_DIR
-Ees.default.path.data=$DATA_DIR -Ees.default.path.conf=$CONF_DIR
retval=$?
echo
[ $retval -eq 0 ] && touch $lockfile
return $retval
}
stop() {
echo -n $"Stopping $prog: "
# stop it here, often "killproc $prog"
killproc -p $pidfile -d ${stopping.timeout} $prog
retval=$?
echo
[ $retval -eq 0 ] && rm -f $lockfile
return $retval
}
2) My original setup used the WAN for the web interface, and a non-routing
inside LAN for transport between the "server" and a second VM running
Graylog. This gave us unlimited search without giving every person on the
master admin access. Now if I try that it redirects to the internal LAN at
login and fails to load. So you access the web page from the WAN, and it
redirects to the LAN address space. I'm foggy on the setup since it was a
year ago or more since I set things up. But somehow I need to get the
second VM talking to the master, and have web access from the WAN. I'm
thinking with 2.x I need multiple network entries someplace I didn't need
it before? As it stands now I have a working Graylog collecting logs and
accepting logins. But the second VM is not working yet. The reason I went
with 2 networks in the first place was to keep traffic between the Graylog
instances internal to the VMware host.
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/graylog2/7dea2d3a-6708-4f24-b8b1-d492519689b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
