+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Support Area (/forum-30.html)
+--- Forum: Update/Upgrade (/forum-44.html)
+--- Thread: RC3->RC4 = no statistics (/thread-2804.html)
RC3->RC4 = no statistics - prale - 03-21-2008 03:21 AM
Hello, my statistics in admin interface is filled with zero's since I updated to RC4.
The reseller and user statistics are working fine, so it is logged.
What can I do?
I already flushed iptables en rebooted, it didn't seems to help.
I think it's a cron problem.
The ispcp_netwerk.log looks like this:
Code:
iptables: Resource temporarily unavailable
iptables: No chain/target/match by that name
iptables: Resource temporarily unavailable
iptables: Resource temporarily unavailable
iptables: No chain/target/match by that name
iptables: Resource temporarily unavailable
iptables: No chain/target/match by that name
iptables: Resource temporarily unavailable
iptables: Resource temporarily unavailable
iptables: Resource temporarily unavailable
iptables: No chain/target/match by that name
iptables: Resource temporarily unavailable
iptables: Resource temporarily unavailable
iptables: Resource temporarily unavailable
iptables: Resource temporarily unavailable
iptables: Invalid argument
iptables v1.3.6: Couldn't load target `ISPCP_INPUT':/lib/iptables/libipt_ISPCP_INPUT.so: cannot open shared object file: No such file or directory
Try `iptables -h' or 'iptables --help' for more information.
iptables v1.3.6: Couldn't load target `ISPCP_OUTPUT':/lib/iptables/libipt_ISPCP_OUTPUT.so: cannot open shared object file: No such file or directory
Try `iptables -h' or 'iptables --help' for more information.
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that nameCode:
# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
fail2ban-apache tcp -- anywhere anywhere tcp dpt:www
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ISPCP_OUTPUT 0 -- anywhere anywhere
Chain ISPCP_INPUT (0 references)
target prot opt source destination
tcp -- anywhere anywhere tcp dpt:imaps
tcp -- anywhere anywhere tcp dpt:pop3s
tcp -- anywhere anywhere tcp dpt:submission
tcp -- anywhere anywhere tcp dpt:smtp
tcp -- anywhere anywhere tcp dpt:imap2
tcp -- anywhere anywhere tcp dpt:pop3
tcp -- anywhere anywhere tcp dpt:https
RETURN 0 -- anywhere anywhere
Chain ISPCP_OUTPUT (1 references)
target prot opt source destination
tcp -- anywhere anywhere tcp spt:imaps
tcp -- anywhere anywhere tcp spt:pop3s
tcp -- anywhere anywhere tcp spt:submission
tcp -- anywhere anywhere tcp spt:smtp
tcp -- anywhere anywhere tcp spt:imap2
tcp -- anywhere anywhere tcp spt:pop3
tcp -- anywhere anywhere tcp spt:https
tcp -- anywhere anywhere tcp spt:www
RETURN 0 -- anywhere anywhere
Chain fail2ban-apache (1 references)
target prot opt source destination
RETURN 0 -- anywhere anywhere
Chain fail2ban-proftpd (0 references)
target prot opt source destination
RETURN 0 -- anywhere anywhere
Chain fail2ban-ssh (0 references)
target prot opt source destination
RETURN 0 -- anywhere anywhereRE: RC3->RC4 = no statistics - prale - 03-21-2008 04:05 AM
Actually I don't see this libipt_ISPCP_INPUT.so
Maybe some files are missing?
Code:
lib/iptables# ls
libip6t_ah.so libipt_CLASSIFY.so libipt_physdev.so
libip6t_connmark.so libipt_CLUSTERIP.so libipt_pkttype.so
libip6t_CONNMARK.so libipt_comment.so libipt_policy.so
libip6t_CONNSECMARK.so libipt_connbytes.so libipt_quota.so
libip6t_dst.so libipt_connlimit.so libipt_realm.so
libip6t_esp.so libipt_connmark.so libipt_recent.so
libip6t_eui64.so libipt_CONNMARK.so libipt_REDIRECT.so
libip6t_frag.so libipt_CONNSECMARK.so libipt_REJECT.so
libip6t_hbh.so libipt_conntrack.so libipt_ROUTE.so
libip6t_hl.so libipt_dccp.so libipt_rpc.so
libip6t_HL.so libipt_DNAT.so libipt_SAME.so
libip6t_icmp6.so libipt_dscp.so libipt_sctp.so
libip6t_ipv6header.so libipt_DSCP.so libipt_SECMARK.so
libip6t_length.so libipt_ecn.so libipt_set.so
libip6t_limit.so libipt_ECN.so libipt_SET.so
libip6t_LOG.so libipt_esp.so libipt_SNAT.so
libip6t_mac.so libipt_hashlimit.so libipt_standard.so
libip6t_mark.so libipt_helper.so libipt_state.so
libip6t_MARK.so libipt_icmp.so libipt_statistic.so
libip6t_multiport.so libipt_iprange.so libipt_string.so
libip6t_NFQUEUE.so libipt_ipv4options.so libipt_TARPIT.so
libip6t_owner.so libipt_IPV4OPTSSTRIP.so libipt_tcpmss.so
libip6t_physdev.so libipt_length.so libipt_TCPMSS.so
libip6t_policy.so libipt_limit.so libipt_tcp.so
libip6t_REJECT.so libipt_LOG.so libipt_tos.so
libip6t_ROUTE.so libipt_mac.so libipt_TOS.so
libip6t_rt.so libipt_mark.so libipt_TRACE.so
libip6t_SECMARK.so libipt_MARK.so libipt_ttl.so
libip6t_standard.so libipt_MASQUERADE.so libipt_TTL.so
libip6t_state.so libipt_MIRROR.so libipt_u32.so
libip6t_tcp.so libipt_multiport.so libipt_udp.so
libip6t_TRACE.so libipt_NETMAP.so libipt_ULOG.so
libip6t_udp.so libipt_NFQUEUE.so libipt_unclean.so
libipt_addrtype.so libipt_NOTRACK.so
libipt_ah.so libipt_owner.soRE: RC3->RC4 = no statistics - prale - 03-22-2008 01:14 AM
Also I found out that the disk limits are not counted.
New accounts stay at 0% since the RC4 upgrade :S
RE: RC3->RC4 = no statistics - joximu - 03-22-2008 01:17 AM
Hi prale
there is no need for the .so files - Maybe you also have a look at this thread:
http://www.isp-control.net/forum/weird-server-statistics-t-2803.html
Where is you ispcp_netwerk.log and from when (date)?
/J
RE: RC3->RC4 = no statistics - prale - 03-22-2008 01:19 AM
Thanxs for fast support
I will try the topic, but I think it's not the same problem since all my stats are zero, and no strange values.
RE: RC3->RC4 = no statistics - prale - 03-22-2008 01:22 AM
Code:
# iptables -L -n -v --line-number
Chain INPUT (policy ACCEPT 139K packets, 38M bytes)
num pkts bytes target prot opt in out source destina tion
1 34850 26M fail2ban-apache tcp -- * * 0.0.0.0/0 0 .0.0.0/0 tcp dpt:80
2 139K 38M ISPCP_INPUT 0 -- * * 0.0.0.0/0 0.0.0 .0/0
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
num pkts bytes target prot opt in out source destina tion
Chain OUTPUT (policy ACCEPT 138K packets, 33M bytes)
num pkts bytes target prot opt in out source destina tion
1 138K 33M ISPCP_OUTPUT 0 -- * * 0.0.0.0/0 0.0. 0.0/0
Chain ISPCP_INPUT (1 references)
num pkts bytes target prot opt in out source destina tion
1 0 0 tcp -- * * 0.0.0.0/0 0.0.0.0 /0 tcp dpt:993
2 0 0 tcp -- * * 0.0.0.0/0 0.0.0.0 /0 tcp dpt:995
3 0 0 tcp -- * * 0.0.0.0/0 0.0.0.0 /0 tcp dpt:587
4 1794 98557 tcp -- * * 0.0.0.0/0 0.0.0.0 /0 tcp dpt:25
5 44 3005 tcp -- * * 0.0.0.0/0 0.0.0.0 /0 tcp dpt:143
6 0 0 tcp -- * * 0.0.0.0/0 0.0.0.0 /0 tcp dpt:110
7 0 0 tcp -- * * 0.0.0.0/0 0.0.0.0 /0 tcp dpt:443
8 34850 26M tcp -- * * 0.0.0.0/0 0.0.0.0 /0 tcp dpt:80
9 139K 38M RETURN 0 -- * * 0.0.0.0/0 0.0.0.0 /0
Chain ISPCP_OUTPUT (1 references)
num pkts bytes target prot opt in out source destina tion
1 0 0 tcp -- * * 0.0.0.0/0 0.0.0.0 /0 tcp spt:993
2 0 0 tcp -- * * 0.0.0.0/0 0.0.0.0 /0 tcp spt:995
3 0 0 tcp -- * * 0.0.0.0/0 0.0.0.0 /0 tcp spt:587
4 1864 117K tcp -- * * 0.0.0.0/0 0.0.0.0 /0 tcp spt:25
5 48 5093 tcp -- * * 0.0.0.0/0 0.0.0.0 /0 tcp spt:143
6 0 0 tcp -- * * 0.0.0.0/0 0.0.0.0 /0 tcp spt:110
7 0 0 tcp -- * * 0.0.0.0/0 0.0.0.0 /0 tcp spt:443
8 34539 22M tcp -- * * 0.0.0.0/0 0.0.0.0 /0 tcp spt:80
9 138K 33M RETURN 0 -- * * 0.0.0.0/0 0.0.0.0 /0
Chain fail2ban-apache (1 references)
num pkts bytes target prot opt in out source destina tion
1 34850 26M RETURN 0 -- * * 0.0.0.0/0 0.0.0.0 /0
Chain fail2ban-proftpd (0 references)
num pkts bytes target prot opt in out source destina tion
1 0 0 RETURN 0 -- * * 0.0.0.0/0 0.0.0.0 /0
Chain fail2ban-ssh (0 references)
num pkts bytes target prot opt in out source destina tion
1 0 0 RETURN 0 -- * * 0.0.0.0/0 0.0.0.0 /0RE: RC3->RC4 = no statistics - joximu - 03-22-2008 01:26 AM
ok
how does your /etc/cron.d/ispcp look like?
/J
RE: RC3->RC4 = no statistics - prale - 03-22-2008 01:30 AM
Code:
# delayed tasks START.
# Quota
@daily root {QUOTA_ROOT_DIR}/ispcp-dsk-quota &>{LOG_DIR}/ispcp-dsk-quota.log
# Traffic
0,30 * * * * root {TRAFF_ROOT_DIR}/ispcp-srv-traff &>{LOG_DIR}/ispcp-srv-traff.log
0,30 * * * * root {TRAFF_ROOT_DIR}/ispcp-vrl-traff &>{LOG_DIR}/ispcp-vrl-traff.log
15,45 * * * * root {TRAFF_ROOT_DIR}/ispcp-vrl-traff-correction &>{LOG_DIR}/ispcp-vrl-traff-correction.log
# customer logs
@daily root {TOOLS_ROOT_DIR}/ispcp-httpd-logs-mngr &>{LOG_DIR}/ispcp-httpd-logs-mngr.log
# Backup
@daily root {BACKUP_ROOT_DIR}/ispcp-backup-all yes &>{LOG_DIR}/ispcp-backup-all-mngr.log
@daily root {BACKUP_ROOT_DIR}/ispcp-backup-ispcp noreport &>{LOG_DIR}/ispcp-backup-ispcp-mngr.log
# Remove config backups older than seven days
@daily root find {CONF_DIR}/*/backup/* -maxdepth 0 -type f -mtime +7 -print | egrep '.*\.[0-9]+$' | xargs -r /bin/rm
# Remove Daemon Logs older than 14 days (except .gz files)
@daily root find {LOG_DIR}/* -maxdepth 1 -type f -mtime +14 -print | egrep '.*\.gz$' | xargs -r /bin/rm
# AWStats
{AW-ENABLED}15 */6 * * * root {AWSTATS_ROOT_DIR}/awstats_updateall.pl now -awstatsprog={AWSTATS_ENGINE_DIR}/awstats.pl >/dev/null 2>&1
# Rootkit Hunter
{RK-ENABLED}0 */12 * * * root {RKHUNTER} --scan-knownbad-files --check-deleted --createlogfile --cronjob --createlogfile {RKHUNTER_LOG} >/dev/null 2>&1
# Chkrootkit
{CR-ENABLED}0 */12 * * * root {CHKROOTKIT} &> {CHKROOTKIT_LOG}
# Look for and purge old sessions every 30 minutes
0,30 * * * * root {TOOLS_ROOT_DIR}/ispcpphptemp.sh >/dev/null 2>&1
# [{DMN_NAME}] backup task START.
# [{DMN_NAME}] backup task END.
# [{DMN_NAME}]:{CRONJOB_ID} custom task START.
# [{DMN_NAME}]:{CRONJOB_ID} custom task END.
# [{DMN_NAME}] AWStats static tasks START.
# [{DMN_NAME}] AWStats static tasks END.
# delayed tasks END.RE: RC3->RC4 = no statistics - joximu - 03-22-2008 01:33 AM
Ok, your not the only one.
The paths are not correct - the {...} should be replaced by the correct values - the setup or update script should do this.
You should have a backup of this file in /etc/ispcp/cron/backup - I think you should be able to correct the paths so it's working again...
/J
RE: RC3->RC4 = no statistics - prale - 03-22-2008 01:41 AM
I hope I see the light now
I'll check the differences now.
Maybe this is caused by the fact I can only stop the daemon the second attempt?
This gave me an error at upgrade because the script only tries to stop it once, and no check if it is really stopped.
maybe this files are used by the daemon so the cant get proper data?