Josh,

Thanks for the reply, but what client? I haven't even added any yet! If you mean the server as a client, I already changed the XYMONDPORT variable. Is there some other variable that needs to be changed? To me, changing this variable should allow everything related to the server to work on a different port.

The only way I've ever been able to make it work on another port is by changing '1984' everywhere in the C code and remaking the system. I was hoping not to have to do that this time. Is there some other configuration setting I'm missing?

David

On Tue, Jul 14, 2015 at 12:38 PM, Josh Luthman <josh at imaginenetworksllc.com> wrote:

Purple means it isn't getting data.

Your client(s) aren't sending to the proper port would be my thought.

Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373

On Tue, Jul 14, 2015 at 12:36 PM, David Welker <dewelker at gmail.com> wrote:

...

I've successfully installed Xymon 4.3.21, but tried to change it from the default port of 1984 by changing the XYMONDPORT variable in xymonserver.cfg. Unfortunately, this turned the cpu, disk, files, etc. all purple. The bbd, conn, http, and xymon status' are all green.. Is there something else I need to change to be able to run Xymon from another port?

Thanks,

David

---

Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon

Josh,

I knew that, but assumed it was all based out of the server directory. Turns out, based on your observation, that I had to actually start the client (after making sure that XYMONDPORT was set in clientlaunch.cfg)!

I think what confused me is that my "client" software is based on a totally different directory with extension scripts, etc., and I hadn't even installed it on this server. Thanks, Josh, for reminding me that the server has it's own "client", even if it did make me feel like a noob! lol

David

On Wed, Jul 15, 2015 at 9:38 AM, Josh Luthman <josh at imaginenetworksllc.com> wrote:

The server install also installs the client. The client reports disk, file, memory, etc tests.

Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Jul 15, 2015 9:30 AM, "David Welker" <dewelker at gmail.com> wrote:

...

Josh,

Thanks for the reply, but what client? I haven't even added any yet! If you mean the server as a client, I already changed the XYMONDPORT variable. Is there some other variable that needs to be changed? To me, changing this variable should allow everything related to the server to work on a different port.

The only way I've ever been able to make it work on another port is by changing '1984' everywhere in the C code and remaking the system. I was hoping not to have to do that this time. Is there some other configuration setting I'm missing?

David

On Tue, Jul 14, 2015 at 12:38 PM, Josh Luthman < josh at imaginenetworksllc.com> wrote:

...

Purple means it isn't getting data.

Your client(s) aren't sending to the proper port would be my thought.

Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373

On Tue, Jul 14, 2015 at 12:36 PM, David Welker <dewelker at gmail.com> wrote:

...

I've successfully installed Xymon 4.3.21, but tried to change it from the default port of 1984 by changing the XYMONDPORT variable in xymonserver.cfg. Unfortunately, this turned the cpu, disk, files, etc. all purple. The bbd, conn, http, and xymon status' are all green.. Is there something else I need to change to be able to run Xymon from another port?

Thanks,

David

---

Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon