Author Topic: Ajuda SARG - Acesso a relatórios  (Read 1102 times)

eversonmrts

  • Zen Apprentice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Ajuda SARG - Acesso a relatórios
« on: December 07, 2015, 02:21:59 pm »
Bom dia!
Gostaria de saber como posso proceder para fazer com que o Sarg funcione no Zentyal. Ja fiz varias tentativas e pesquisas porem nada adiantou.
Segue arquivos:

>sarg.conf
# sarg.conf
#
# A linguagem do relatório fica a seu critério
#language Portuguese
# o caminho do arquivo de log do squid
access_log /var/log/squid3/access.log
# O título do seu relatório ou seja o nome que você quiser apresentar no relatório
title "Relatório Acessos Scavaseg"
# A fonte do relatório
font_face Tahoma,Verdana,Arial
header_color darkblue
header_bgcolor blanchedalmond
# tamanho da font
font_size 9px
# cor de fundo do relatório
background_color white
text_color #000000
text_bgcolor lavender
title_color green
# Arquivo temporário do sarg
temporary_dir /tmp
#caminho que gerará os relatórios.
output_dir /var/www/html/squid-reports
resolve_ip yes
user_ip no
topuser_sort_field BYTES reverse
user_sort_field BYTES reverse
exclude_users /etc/sarg/exclude_users
exclude_hosts /etc/sarg/exclude_hosts
date_format u
lastlog 0
remove_temp_files yes
index yes
index_tree file
overwrite_report yes
records_without_userid ip
use_comma yes
mail_utility mail
# O número de sites que irá exibir no relatório.
topsites_num 100
topsites_sort_order CONNECT D
index_sort_order D
exclude_codes /etc/sarg/exclude_codes
max_elapsed 28800000
# Todo conteúdo a ser exibido pelo sarg aqui você pode deixar bem enxuto seu relatório,
# ou seja, mostrar apenas as maiores necessidades.
report_type topusers topsites sites_users users_sites date_time denied auth_failures site_user_time_date downloads
usertab /etc/sarg/usertab
# Nesta linha mude para yes para evitar futuros problemas de desfragmentação ainda não descoberto.
long_url no
date_time_by bytes

>apache2.conf:

# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
Mutex file:${APACHE_LOCK_DIR} default

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 5


# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off
# LogLevel: Control the severity of messages logged to the error_log.
# Available values: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the log level for particular modules, e.g.
# "LogLevel info ssl:warn"
#
LogLevel warn

# Include module configuration:
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf

# Include list of ports to listen on
Include ports.conf


# Sets the default security model of the Apache2 HTTPD server. It does
# not allow access to the root filesystem outside of /usr/share and /var/www.
# The former is used by web applications packaged in Debian,
# the latter may be used for local directories served by the web server. If
# your system is serving content from a sub-directory in /srv you must allow
# access here, or in any related virtual host.
<Directory />
        Options FollowSymLinks
        AllowOverride None
        Require all denied
</Directory>

<Directory /usr/share>
        AllowOverride None
        Require all granted
</Directory>

<Directory /var/www/>
        Options Indexes FollowSymLinks
        AllowOverride None
        Require all granted
</Directory>

#TESTE SARG
<Directory /var/www/html/squid-reports>
order allow,deny
allow from 192.168.0.0/24
allow from 127.0.0.1
allow from localhost
# Add additional allowed hosts as needed
# allow from .example.com
</Directory>

___________________________________________________________________________________________________________________

Ja dei permissoes na pasta /var/www/html/squid-reports
Serviço apache2 rodando
Tirei passagem do proxy para o ip local.
O que fazer, alguem pode ajudar?

Obrigado