Just reporting back to say that I successfully reinstalled everything to the SSD over the weekend. Pulled the old drive on Monday, and everything has been working well with the upgraded drive.

Youtube Video

@DustinB3403 said:

So this script should work.

Going to update my script and test.

Just updated to 4.13 using your script.

You guys are brutal!

In the past, I've read that it is critical to backup the metadata from your XS host. Has this changed at all with the usage of XO? If not, is there a mechanism in XO to capture the host's metadata?

Thx, Dan

Youtube Video

@scottalanmiller I just noticed that I was the last one to comment in that thread.

I think the other important thing to remember is that XO is open source, so the development, testing, and deployment process is more visible than you would see with similar products from Unitrends or Veeam.

I own one. Works fine for my home needs.

To enable the service at startup, issue the command sudo systemctl enable xo-server.service. You can also check the service status with sudo systemctl status xo-server.service and manually start the service with sudo systemctl start xo-server.service

HTH, Dan

I know there are a bunch of XO users here. I would appreciate it if you could take a look and see if you can replicate the issue described here.

Thanks, Dan

Youtube Video

I have my XO VM setup to pass logs to my ELK server using filebeat. Occasionally, it just stops working. On the XO logs I see:

Mar 11 08:20:48 xo-stable /usr/bin/filebeat[26957]: transport.go:125: SSL client failed to connect with: dial tcp 192.168.xxx.xxx:5044: getsockopt: connection refused

Here's the info on the elasticsearch service:

[root@localhost ~]# systemctl status elasticsearch
● elasticsearch.service - Elasticsearch
   Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2016-03-09 08:53:02 CST; 1 day 23h ago
     Docs: http://www.elastic.co
  Process: 1218 ExecStartPre=/usr/share/elasticsearch/bin/elasticsearch-systemd-pre-exec (code=exited, status=0/SUCCESS)
 Main PID: 1233 (java)
   CGroup: /system.slice/elasticsearch.service
           └─1233 /bin/java -Xms256m -Xmx1g -Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -X...

Mar 09 08:53:25 localhost.localdomain elasticsearch[1233]: [2016-03-09 08:53:25,194][INFO ][http                     ] [Nicholas Maunder] publish_address {localhost/127.0.0.1:9200}, bound_addresses {127...., {[::1]:9200}
Mar 09 08:53:25 localhost.localdomain elasticsearch[1233]: [2016-03-09 08:53:25,195][INFO ][node                     ] [Nicholas Maunder] started
Mar 09 08:53:27 localhost.localdomain elasticsearch[1233]: [2016-03-09 08:53:27,238][INFO ][gateway                  ] [Nicholas Maunder] recovered [12] indices into cluster_state
Mar 09 08:53:52 localhost.localdomain elasticsearch[1233]: [2016-03-09 08:53:52,642][INFO ][cluster.routing.allocation] [Nicholas Maunder] Cluster health status changed from [RED] to [YELLOW] (reason: [s...28][3]] ...]).
Mar 09 18:00:05 localhost.localdomain elasticsearch[1233]: [2016-03-09 18:00:05,868][INFO ][cluster.metadata         ] [Nicholas Maunder] [filebeat-2016.03.10] creating index, cause [auto(bulk api)], tem...default_, log]
Mar 09 18:00:06 localhost.localdomain elasticsearch[1233]: [2016-03-09 18:00:06,396][INFO ][cluster.metadata         ] [Nicholas Maunder] [filebeat-2016.03.10] update_mapping [log]
Mar 09 18:00:06 localhost.localdomain elasticsearch[1233]: [2016-03-09 18:00:06,439][INFO ][cluster.routing.allocation] [Nicholas Maunder] Cluster health status changed from [RED] to [YELLOW] (reason: [s...10][4]] ...]).
Mar 10 18:00:11 localhost.localdomain elasticsearch[1233]: [2016-03-10 18:00:11,665][INFO ][cluster.metadata         ] [Nicholas Maunder] [filebeat-2016.03.11] creating index, cause [auto(bulk api)], tem...default_, log]
Mar 10 18:00:12 localhost.localdomain elasticsearch[1233]: [2016-03-10 18:00:12,332][INFO ][cluster.routing.allocation] [Nicholas Maunder] Cluster health status changed from [RED] to [YELLOW] (reason: [s...11][4]] ...]).
Mar 10 18:00:12 localhost.localdomain elasticsearch[1233]: [2016-03-10 18:00:12,356][INFO ][cluster.metadata         ] [Nicholas Maunder] [filebeat-2016.03.11] update_mapping [log]

And the logstash service:

[root@localhost ~]# systemctl status logstash
● logstash.service - LSB: Starts Logstash as a daemon.
   Loaded: loaded (/etc/rc.d/init.d/logstash)
   Active: active (exited) since Wed 2016-03-09 08:53:02 CST; 1 day 23h ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1221 ExecStart=/etc/rc.d/init.d/logstash start (code=exited, status=0/SUCCESS)

Mar 09 08:53:02 localhost.localdomain systemd[1]: Starting LSB: Starts Logstash as a daemon....
Mar 09 08:53:02 localhost.localdomain logstash[1221]: logstash started.
Mar 09 08:53:02 localhost.localdomain systemd[1]: Started LSB: Starts Logstash as a daemon..

Thoughts / suggestions on how to troubleshoot this?

Did it fire up? If so, probably right

So, my earlier change was not correct. Found this in the logstash.err file -- No such command "LS_HEAP_SIZE=2g" .

How are you starting Logstash?

I followed your instructions to build the ELK server, so everything is handled by systemd.

If you look in /etc/init.d/logstash, the start script has the heap size hard coded there. If you are starting from the system, you will need to change it there, I'm sure.

I missed that yesterday when I examined that file.Thanks!

I recently secured a domain from a company (buydomains.com) that had previously registered it and had it listed for sale. It was listed for $2,288. I forget my initial offer, but it was either $500 or $750. They countered @ $1,716.

I offered $1,000 and explained that this was the max I was authorized to spend. He was able to "take it to management" and get it approved. I'm sure we both were being less than honest, but the bottom line is that you should be able to negotiate this yourself.

$12k seems really high. Can you share the proposed URL?

Act! Premium for Workroups