PDA

View Full Version : True64/OSF1 agents compilation issue


LEM
10-11-2004, 18:05
Hi all,

I faced some problems compiling zabbix 1.0 agents (agent, agentd and sender) on my True64 (OSF1 V5.1 1885 alpha) using Compac C compiler (Compaq C V6.4-014 on Compaq Tru64 UNIX V5.1A (Rev. 1885) - Compiler Driver V6.4-215 (sys) cc Driver)

Makefile of src/agent/: option Wall not supported
Option Wall is not supported with this version of CC, so You have to remove them to make 'make' run. That's wath I've done to build them.

Agent(d): lot of options not supported
When building and linking ('make'), lots of warning are generated, mainly regarding args for printf in some includes file, but build is ok.
Anyway, when you use the binaries, lots of keys are not usables (load, load5, load15, memory usage, ...). I guess it's linked.

Has anybody already had this issue? Is she fixed in later releases?

example of the make warnings:

Script started on Tue Nov 9 18:17:19 2004
# make^M
cc -o ../../bin/zabbix_agent -g -I../../include zabbix_agent.c sysinfo.c ../../include/log.c ../../include/cfg.c ../../includ
e/security.c ../../include/snprintf.c^M
zabbix_agent.c:^M
sysinfo.c:^M
../../include/log.c:^M
cc: Warning: ../../include/log.c, line 61: In this statement, this argument to fprintf contains a bad conversion specification
"%m" that will cause unpredictable behavior. (badconvspec)^M
fprintf(stderr, "Unable to open debug file [%s] [%m]\n", filename);^M
----------------------------------------^^M
cc: Info: ../../include/log.c, line 103: In this statement, an array is being accessed outside the bounds specified for the ar
ray type. (subscrbounds)^M
str[MAX_STRING_LEN]=0;^M
--------------------^^M
../../include/cfg.c:^M
cc: Warning: ../../include/cfg.c, line 62: In this statement, this argument to fprintf contains a bad conversion specification
"%m" that will cause unpredictable behavior. (badconvspec)^M
fprintf(stderr, "Cannot open config file [%s] [%m]\n",cfg_file);^M
--------------------------------^^M
../../include/security.c:^M
../../include/snprintf.c:^M
cc -o ../../bin/zabbix_agentd -g -I../../include zabbix_agentd.c sysinfo.c stats.c interfaces.c diskdevices.c ../../include/lo
g.c ../../include/cfg.c ../../include/security.c ../../include/pid.c ../../include/snprintf.c^M
zabbix_agentd.c:^M
sysinfo.c:^M
stats.c:^M
cc: Warning: stats.c, line 76: In this statement, this argument to fprintf contains a bad conversion specification "%m" that w
ill cause unpredictable behavior. (badconvspec)^M
fprintf(stderr, "Cannot open file [%s] [%m]\n","/tmp/zabbix_agentd.tmp2");^M
----------------------------------------^^M
interfaces.c:^M
cc: Warning: interfaces.c, line 112: In this statement, this argument to fprintf contains a bad conversion specification "%m"
that will cause unpredictable behavior. (badconvspec)^M
fprintf(stderr, "Cannot open config file [%s] [%m]\n","/proc/net/dev");^M
--------------------------------^^M
cc: Warning: interfaces.c, line 347: In this statement, this argument to fprintf contains a bad conversion specification "%m"
that will cause unpredictable behavior. (badconvspec)^M
fprintf(stderr, "Cannot open config file [%s] [%m]\n","/proc/net/dev");^M

Alexei
18-11-2004, 19:18
I've never tried to compile ZABBIX under Tru64. Actually I'm very interested to get remote access to a Tru64 system running on Alpha hardware to fix any compilation problems.

Please, let me know if it's possible.

LEM
18-11-2004, 19:35
Actually I'm very interested to get remote access to a Tru64 system running on Alpha hardware to fix any compilation problems.

Please, let me know if it's possible.

Remote access won't be possible and I have'nt got any spare hardware to set on a 'public' dmz :-(

Anyway, I can spend some time via IRC if interrested, as you're welcome in our datacenter too (france/near paris) :)

LEM
18-11-2004, 20:03
Remote access won't be possible and I have'nt got any spare hardware to set on a 'public' dmz :-(


Well, a solution is rarely longer than a good googlesearch away: See HP Test Drive program (http://www.testdrive.compaq.com/os/#tru64) which allow freely access (shell account) to tru64 servers.

The HP Test Drive program should help's pass tests on differents archi & os for zabbix release cycle, isn't it?


Anyway, I can spend some time via IRC if interrested, as you're welcome in our datacenter too (france/near paris) :)

Anway, You're always welcome in france ;-)

Alexei
18-11-2004, 23:03
Thanks for pointing to the HP Test Drive program.:cool: I hope it works.

By the way, I've never seen rack-mounted Tru64 servers. Just wondering if such servers exist...

LEM
19-11-2004, 00:09
Thanks for pointing to the HP Test Drive program.:cool: I hope it works.


yes, it works fine as long as no root privileges nor outbound connexions are needed. To just run compil tests, there's no pb.

Test the 'zabbix' user account you've received by mail :-)


By the way, I've never seen rack-mounted Tru64 servers. Just wondering if such servers exist...

Sure this kind of box exists, see
this link (description of alpha servers availables thru the HP Test Drive program) (http://www.testdrive.compaq.com/systems/alpha.shtml) . If you want to have more field pics, I'll take some photos of this part of the datacenter next time :-)

Alexei
19-11-2004, 10:04
Thanks! I've got a couple of emails from the HP Test Drive. By the way, they provide access to whole range of OS and hardware platforms supported by HP and former Compaq, including Tru64, HP-UX, OpenVMS, and Linux.

LEM
19-11-2004, 10:41
By the way, they provide access to whole range of OS and hardware platforms supported by HP and former Compaq, including Tru64, HP-UX, OpenVMS, and Linux.

Yes! So, I guess we could use HP TD program to help zabbix release cycle to undergo some compilation tests and packagings on differents os flavors. Especially for zabbix agents (tru64, hp-ux, openvms, solaris, 4 majors linux distros, ...).

Alexei
20-11-2004, 14:38
Just tried to compile ZABBIX 1.1alpha1 under V5.1 2650 alpha, no problems at all! I do not expect any (perhaps some 64-bit issues may exist) issues with ZABBIX v1.0 as well.

I would suggest using of GCC compiler. Standard CC obviously relies on ANSI standard, which is not compatible with ZABBIX sources.

Alexei
21-11-2004, 14:12
Pre-compiled Tru64/OSF agents are available from http://www.zabbix.com/download.php

LEM
21-11-2004, 20:21
Just tried to compile ZABBIX 1.1alpha1 under V5.1 2650 alpha, no problems at all! I do not expect any (perhaps some 64-bit issues may exist) issues with ZABBIX v1.0 as well.


Well, I tried compilation of v1.0 on these (HPTD program) 5.1B and it was fine (no error), but I saw no sysctl.h support... I'me going to test statically linked binaries on my 5.1A, just to see if ok (stats) and if all parameters are managed by the zabbix agent(d): load and memory use are collected using sysctl...


I would suggest using of GCC compiler. Standard CC obviously relies on ANSI standard, which is not compatible with ZABBIX sources.

Hum... will try.

Alexei
21-11-2004, 20:41
At the moment, ZABBIX agent does not support monitoring of most of basic metrics under Tru64/OSF.

I have just released ZABBIX Manual for v1.1 (alpha), see http://www.zabbix.com/manual/v1.1/config_items.php for more details about supported parameters by platform.