bugzilla-daemon | 16 Apr 19:32 2015

[Bug 8911] CLOSED WONTFIX

Please DO NOT REPLY to this mail or send email to the developers about this bug.

Please follow-up to Bugzilla via Bug 8911.

Have you checked the Frequently Asked Questions (FAQ)?

Please also take the time to read "How to Report Bugs Effectively"
Bug ID Summary Classification Product Version Hardware OS Status Severity Priority Component Assignee Reporter QA Contact
8911
CLOSED WONTFIX
Contribs
SME Contribs
9.0
---
---
UNCONFIRMED
normal
P3
smeserver-phpki
daniel <at> firewall-services.com
junruhuangwork <at> gmail.com
contribteam <at> lists.contribs.org

When first time to open PHPKI in certificate management, but we have no information for initializing root certificate data, it's just stopped like this: Creating PHPki file store... Writing configuration files... Creating root certificate... On the server, we can't see the page of certificate management
You are receiving this mail because:
  • You are the QA Contact for the bug.
<div>
Please DO NOT REPLY to this mail or send email to the developers about this bug.<br><br>
Please follow-up to Bugzilla via <a class="bz_bug_link 
          bz_status_UNCONFIRMED " title="UNCONFIRMED - CLOSED WONTFIX" href="http://bugs.contribs.org/show_bug.cgi?id=8911">Bug 8911</a>.<br><br>
Have you checked the <a href="http://wiki.contribs.org/SME_Server:Documentation:FAQ">Frequently Asked Questions (FAQ)</a>?<br><br>
Please also take the time to read "<a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">How to Report Bugs Effectively</a>"<br><table border="1" cellspacing="0" cellpadding="8">
<tr>Bug ID
          <td>
<a class="bz_bug_link 
          bz_status_UNCONFIRMED " title="UNCONFIRMED - CLOSED WONTFIX" href="http://bugs.contribs.org/show_bug.cgi?id=8911">8911</a>
          </td>
        </tr>
<tr>Summary
          <td>CLOSED WONTFIX
          </td>
        </tr>
<tr>Classification
          <td>Contribs
          </td>
        </tr>
<tr>Product
          <td>SME Contribs
          </td>
        </tr>
<tr>Version
          <td>9.0
          </td>
        </tr>
<tr>Hardware
          <td>---
          </td>
        </tr>
<tr>OS
          <td>---
          </td>
        </tr>
<tr>Status
          <td>UNCONFIRMED
          </td>
        </tr>
<tr>Severity
          <td>normal
          </td>
        </tr>
<tr>Priority
          <td>P3
          </td>
        </tr>
<tr>Component
          <td>smeserver-phpki
          </td>
        </tr>
<tr>Assignee
          <td>daniel <at> firewall-services.com
          </td>
        </tr>
<tr>Reporter
          <td>junruhuangwork <at> gmail.com
          </td>
        </tr>
<tr>QA Contact
          <td>contribteam <at> lists.contribs.org
          </td>
        </tr>
</table>
<p>
        </p>
<div>
        When first time to open PHPKI in certificate management, but we have no
information for initializing root certificate data, it's just stopped like
this:
 Creating PHPki file store...
 Writing configuration files...
 Creating root certificate...

On the server, we can't see the page of certificate management
        </div>

      <span>You are receiving this mail because:</span>

      <ul>
<li>You are the QA Contact for the bug.</li>
      </ul>
</div>
bugzilla-daemon | 16 Apr 17:36 2015

[Bug 8910] SARG uses only the last access.log: rotated files are named unexpectedly

Please DO NOT REPLY to this mail or send email to the developers about this bug.

Please follow-up to Bugzilla via Bug 8910.

Have you checked the Frequently Asked Questions (FAQ)?

Please also take the time to read "How to Report Bugs Effectively"
Bug ID Summary Classification Product Version Hardware OS Status Severity Priority Component Assignee Reporter QA Contact
8910
SARG uses only the last access.log: rotated files are named unexpectedly
Contribs
SME Contribs
9.0
---
---
UNCONFIRMED
normal
P3
smeserver-sarg
mastersleepy <at> vanhees.cc
michel <at> gadis.it
contribteam <at> lists.contribs.org

I noticed that Sarg missed data in its analysis. This is because Sarg expects archived log files to be named like *SME8* [root <at> proxy2 ~]# ll /var/log/squid -lh totale 21M -rw-r----- 1 squid squid 581K 16 apr 12:29 access.log -rw-r----- 1 squid squid 23K 12 apr 04:02 access.log.1.gz -rw-r----- 1 squid squid 35K 5 apr 04:02 access.log.2.gz -rw-r----- 1 squid squid 41K 29 mar 04:02 access.log.3.gz -rw-r----- 1 squid squid 2,2M 22 mar 04:02 access.log.4.gz -rw-r----- 1 squid squid 3,0M 15 mar 04:02 access.log.5.gz instead, on the new installation *SME9* they are named [root <at> xxx ~]# ll /var/log/squid total 73760 -rw-r----- 1 squid squid 48085906 Apr 16 17:26 access.log -rw-r----- 1 squid squid 1399311 Mar 15 03:43 access.log-20150315.gz -rw-r----- 1 squid squid 4180100 Mar 22 03:35 access.log-20150322.gz -rw-r----- 1 squid squid 6619389 Mar 29 03:06 access.log-20150329.gz -rw-r----- 1 squid squid 6685243 Apr 5 03:11 access.log-20150405.gz -rw-r----- 1 squid squid 5758931 Apr 12 03:43 access.log-20150412.gz so the sarg cron does not find any access.log files except the first.
You are receiving this mail because:
  • You are the QA Contact for the bug.
<div>
Please DO NOT REPLY to this mail or send email to the developers about this bug.<br><br>
Please follow-up to Bugzilla via <a class="bz_bug_link 
          bz_status_UNCONFIRMED " title="UNCONFIRMED - SARG uses only the last access.log: rotated files are named unexpectedly" href="http://bugs.contribs.org/show_bug.cgi?id=8910">Bug 8910</a>.<br><br>
Have you checked the <a href="http://wiki.contribs.org/SME_Server:Documentation:FAQ">Frequently Asked Questions (FAQ)</a>?<br><br>
Please also take the time to read "<a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">How to Report Bugs Effectively</a>"<br><table border="1" cellspacing="0" cellpadding="8">
<tr>Bug ID
          <td>
<a class="bz_bug_link 
          bz_status_UNCONFIRMED " title="UNCONFIRMED - SARG uses only the last access.log: rotated files are named unexpectedly" href="http://bugs.contribs.org/show_bug.cgi?id=8910">8910</a>
          </td>
        </tr>
<tr>Summary
          <td>SARG uses only the last access.log: rotated files are named unexpectedly
          </td>
        </tr>
<tr>Classification
          <td>Contribs
          </td>
        </tr>
<tr>Product
          <td>SME Contribs
          </td>
        </tr>
<tr>Version
          <td>9.0
          </td>
        </tr>
<tr>Hardware
          <td>---
          </td>
        </tr>
<tr>OS
          <td>---
          </td>
        </tr>
<tr>Status
          <td>UNCONFIRMED
          </td>
        </tr>
<tr>Severity
          <td>normal
          </td>
        </tr>
<tr>Priority
          <td>P3
          </td>
        </tr>
<tr>Component
          <td>smeserver-sarg
          </td>
        </tr>
<tr>Assignee
          <td>mastersleepy <at> vanhees.cc
          </td>
        </tr>
<tr>Reporter
          <td>michel <at> gadis.it
          </td>
        </tr>
<tr>QA Contact
          <td>contribteam <at> lists.contribs.org
          </td>
        </tr>
</table>
<p>
        </p>
<div>
        I noticed that Sarg missed data in its analysis.

This is because Sarg expects archived log files to be named like

*SME8*

[root <at> proxy2 ~]# ll /var/log/squid -lh
totale 21M
-rw-r----- 1 squid squid 581K 16 apr 12:29 access.log
-rw-r----- 1 squid squid  23K 12 apr 04:02 access.log.1.gz
-rw-r----- 1 squid squid  35K  5 apr 04:02 access.log.2.gz
-rw-r----- 1 squid squid  41K 29 mar 04:02 access.log.3.gz
-rw-r----- 1 squid squid 2,2M 22 mar 04:02 access.log.4.gz
-rw-r----- 1 squid squid 3,0M 15 mar 04:02 access.log.5.gz

instead, on the new installation *SME9* they are named

[root <at> xxx ~]# ll /var/log/squid
total 73760
-rw-r----- 1 squid squid 48085906 Apr 16 17:26 access.log
-rw-r----- 1 squid squid  1399311 Mar 15 03:43 access.log-20150315.gz
-rw-r----- 1 squid squid  4180100 Mar 22 03:35 access.log-20150322.gz
-rw-r----- 1 squid squid  6619389 Mar 29 03:06 access.log-20150329.gz
-rw-r----- 1 squid squid  6685243 Apr  5 03:11 access.log-20150405.gz
-rw-r----- 1 squid squid  5758931 Apr 12 03:43 access.log-20150412.gz

so the sarg cron does not find any access.log files except the first.
        </div>

      <span>You are receiving this mail because:</span>

      <ul>
<li>You are the QA Contact for the bug.</li>
      </ul>
</div>
bugzilla-daemon | 13 Apr 11:25 2015

[Bug 8906] server.conf is not correct for the latest version of Zarafa

Please DO NOT REPLY to this mail or send email to the developers about this bug.

Please follow-up to Bugzilla via Bug 8906.

Have you checked the Frequently Asked Questions (FAQ)?

Please also take the time to read "How to Report Bugs Effectively"
Bug ID Summary Classification Product Version Hardware OS Status Severity Priority Component Assignee Reporter QA Contact
8906
server.conf is not correct for the latest version of Zarafa
Contribs
SME Contribs
9.0
---
---
UNCONFIRMED
normal
P3
smeserver-zarafa-unix
paul <at> smeserverpro.com
garth <at> gkcomputerservices.com
contribteam <at> lists.contribs.org

I just install the latest version of Zarafa 7.1.12-48726 and found that the server component would not start. The error is: [root <at> caine zarafa]# service zarafa-server start Starting zarafa-server: Config error: Unknown option 'server_ssl_enable_v2' found! Server shutdown complete. [FAILED] I got it to work by commenting out the server_ssl_enable_v2 option and adding the options from here: https://community.zarafa.com/pg/blog/read/28200/7112-beta2-available the server then started.
You are receiving this mail because:
  • You are the QA Contact for the bug.
<div>
Please DO NOT REPLY to this mail or send email to the developers about this bug.<br><br>
Please follow-up to Bugzilla via <a class="bz_bug_link 
          bz_status_UNCONFIRMED " title="UNCONFIRMED - server.conf is not correct for the latest version of Zarafa" href="http://bugs.contribs.org/show_bug.cgi?id=8906">Bug 8906</a>.<br><br>
Have you checked the <a href="http://wiki.contribs.org/SME_Server:Documentation:FAQ">Frequently Asked Questions (FAQ)</a>?<br><br>
Please also take the time to read "<a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">How to Report Bugs Effectively</a>"<br><table border="1" cellspacing="0" cellpadding="8">
<tr>Bug ID
          <td>
<a class="bz_bug_link 
          bz_status_UNCONFIRMED " title="UNCONFIRMED - server.conf is not correct for the latest version of Zarafa" href="http://bugs.contribs.org/show_bug.cgi?id=8906">8906</a>
          </td>
        </tr>
<tr>Summary
          <td>server.conf is not correct for the latest version of Zarafa
          </td>
        </tr>
<tr>Classification
          <td>Contribs
          </td>
        </tr>
<tr>Product
          <td>SME Contribs
          </td>
        </tr>
<tr>Version
          <td>9.0
          </td>
        </tr>
<tr>Hardware
          <td>---
          </td>
        </tr>
<tr>OS
          <td>---
          </td>
        </tr>
<tr>Status
          <td>UNCONFIRMED
          </td>
        </tr>
<tr>Severity
          <td>normal
          </td>
        </tr>
<tr>Priority
          <td>P3
          </td>
        </tr>
<tr>Component
          <td>smeserver-zarafa-unix
          </td>
        </tr>
<tr>Assignee
          <td>paul <at> smeserverpro.com
          </td>
        </tr>
<tr>Reporter
          <td>garth <at> gkcomputerservices.com
          </td>
        </tr>
<tr>QA Contact
          <td>contribteam <at> lists.contribs.org
          </td>
        </tr>
</table>
<p>
        </p>
<div>
        I just install the latest version of Zarafa 7.1.12-48726 and found that the
server component would not start. The error is:

[root <at> caine zarafa]# service zarafa-server start
Starting zarafa-server: Config error: Unknown option 'server_ssl_enable_v2'
found!
Server shutdown complete.
                                                           [FAILED]

I got it to work by commenting out the server_ssl_enable_v2 option and adding
the options from here:
<a href="https://community.zarafa.com/pg/blog/read/28200/7112-beta2-available">https://community.zarafa.com/pg/blog/read/28200/7112-beta2-available</a> the server
then started.
        </div>

      <span>You are receiving this mail because:</span>

      <ul>
<li>You are the QA Contact for the bug.</li>
      </ul>
</div>
bugzilla-daemon | 9 Apr 16:28 2015

[Bug 8905] qmail-inject: fatal: qq write error or disk full (#4.3.0)

Please DO NOT REPLY to this mail or send email to the developers about this bug.

Please follow-up to Bugzilla via Bug 8905.

Have you checked the Frequently Asked Questions (FAQ)?

Please also take the time to read "How to Report Bugs Effectively"
Bug ID Summary Classification Product Version Hardware OS Status Severity Priority Component Assignee Reporter QA Contact
8905
qmail-inject: fatal: qq write error or disk full (#4.3.0)
Contribs
SME Contribs
8.1
---
---
UNCONFIRMED
normal
P3
smeserver-affa (unmaintained)
arnaud056 <at> guedel.eu
twijtzes <at> foodconsult.nl
contribteam <at> lists.contribs.org

After installing on a fresh 8.1 server as a a backupserver using wget http://www.guedel.eu/telechargements/affa_V3/smeserver-Affa-3.2.2.2-0.noarch.rpm having created a conf file with the settings as recommended in the wiki-contribs affa v 3 description following the described steps running the job; resulted in the setup of the directory structure on the backupserver, as required. But when the files are copied, the error qmail-inject: fatal: qq write error or disk full (#4.3.0) appears. What to do ?
You are receiving this mail because:
  • You are the QA Contact for the bug.
<div>
Please DO NOT REPLY to this mail or send email to the developers about this bug.<br><br>
Please follow-up to Bugzilla via <a class="bz_bug_link 
          bz_status_UNCONFIRMED " title="UNCONFIRMED - qmail-inject: fatal: qq write error or disk full (#4.3.0)" href="http://bugs.contribs.org/show_bug.cgi?id=8905">Bug 8905</a>.<br><br>
Have you checked the <a href="http://wiki.contribs.org/SME_Server:Documentation:FAQ">Frequently Asked Questions (FAQ)</a>?<br><br>
Please also take the time to read "<a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">How to Report Bugs Effectively</a>"<br><table border="1" cellspacing="0" cellpadding="8">
<tr>Bug ID
          <td>
<a class="bz_bug_link 
          bz_status_UNCONFIRMED " title="UNCONFIRMED - qmail-inject: fatal: qq write error or disk full (#4.3.0)" href="http://bugs.contribs.org/show_bug.cgi?id=8905">8905</a>
          </td>
        </tr>
<tr>Summary
          <td>qmail-inject: fatal: qq write error or disk full (#4.3.0)
          </td>
        </tr>
<tr>Classification
          <td>Contribs
          </td>
        </tr>
<tr>Product
          <td>SME Contribs
          </td>
        </tr>
<tr>Version
          <td>8.1
          </td>
        </tr>
<tr>Hardware
          <td>---
          </td>
        </tr>
<tr>OS
          <td>---
          </td>
        </tr>
<tr>Status
          <td>UNCONFIRMED
          </td>
        </tr>
<tr>Severity
          <td>normal
          </td>
        </tr>
<tr>Priority
          <td>P3
          </td>
        </tr>
<tr>Component
          <td>smeserver-affa (unmaintained)
          </td>
        </tr>
<tr>Assignee
          <td>arnaud056 <at> guedel.eu
          </td>
        </tr>
<tr>Reporter
          <td>twijtzes <at> foodconsult.nl
          </td>
        </tr>
<tr>QA Contact
          <td>contribteam <at> lists.contribs.org
          </td>
        </tr>
</table>
<p>
        </p>
<div>
        After installing on a fresh 8.1 server as a a backupserver

using wget
<a href="http://www.guedel.eu/telechargements/affa_V3/smeserver-Affa-3.2.2.2-0.noarch.rpm">http://www.guedel.eu/telechargements/affa_V3/smeserver-Affa-3.2.2.2-0.noarch.rpm</a>

having created a conf file with the settings as recommended in the
wiki-contribs affa v 3 description

following the described steps
running the job;

resulted in the setup of the directory structure on the backupserver, as
required. But when the files are copied, the error

qmail-inject: fatal: qq write error or disk full (#4.3.0)

appears.

What to do ?
        </div>

      <span>You are receiving this mail because:</span>

      <ul>
<li>You are the QA Contact for the bug.</li>
      </ul>
</div>
bugzilla-daemon | 8 Apr 15:46 2015

[Bug 8904] affa --send-keys not working on non standard ssh port

Please DO NOT REPLY to this mail or send email to the developers about this bug.

Please follow-up to Bugzilla via Bug 8904.

Have you checked the Frequently Asked Questions (FAQ)?

Please also take the time to read "How to Report Bugs Effectively"
Bug ID Summary Classification Product Version Hardware OS Status Severity Priority Component Assignee Reporter QA Contact
8904
affa --send-keys not working on non standard ssh port
Contribs
SME Contribs
9.0
---
---
UNCONFIRMED
normal
P3
smeserver-affa (unmaintained)
arnaud056 <at> guedel.eu
keith <at> slater.fr
contribteam <at> lists.contribs.org

I'm using smeserver-affa-3.2.2.2-0.noarch.rpm affa --send-key JOB_NAME does not take the remote ssh port into account. I modified /sbin/affa line 2351 on my backup machine in the sendKeys() subroutine and added -p $job{'sshPort'} This fixed the issue.
You are receiving this mail because:
  • You are the QA Contact for the bug.
<div>
Please DO NOT REPLY to this mail or send email to the developers about this bug.<br><br>
Please follow-up to Bugzilla via <a class="bz_bug_link 
          bz_status_UNCONFIRMED " title="UNCONFIRMED - affa --send-keys not working on non standard ssh port" href="http://bugs.contribs.org/show_bug.cgi?id=8904">Bug 8904</a>.<br><br>
Have you checked the <a href="http://wiki.contribs.org/SME_Server:Documentation:FAQ">Frequently Asked Questions (FAQ)</a>?<br><br>
Please also take the time to read "<a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">How to Report Bugs Effectively</a>"<br><table border="1" cellspacing="0" cellpadding="8">
<tr>Bug ID
          <td>
<a class="bz_bug_link 
          bz_status_UNCONFIRMED " title="UNCONFIRMED - affa --send-keys not working on non standard ssh port" href="http://bugs.contribs.org/show_bug.cgi?id=8904">8904</a>
          </td>
        </tr>
<tr>Summary
          <td>affa --send-keys not working on non standard ssh port
          </td>
        </tr>
<tr>Classification
          <td>Contribs
          </td>
        </tr>
<tr>Product
          <td>SME Contribs
          </td>
        </tr>
<tr>Version
          <td>9.0
          </td>
        </tr>
<tr>Hardware
          <td>---
          </td>
        </tr>
<tr>OS
          <td>---
          </td>
        </tr>
<tr>Status
          <td>UNCONFIRMED
          </td>
        </tr>
<tr>Severity
          <td>normal
          </td>
        </tr>
<tr>Priority
          <td>P3
          </td>
        </tr>
<tr>Component
          <td>smeserver-affa (unmaintained)
          </td>
        </tr>
<tr>Assignee
          <td>arnaud056 <at> guedel.eu
          </td>
        </tr>
<tr>Reporter
          <td>keith <at> slater.fr
          </td>
        </tr>
<tr>QA Contact
          <td>contribteam <at> lists.contribs.org
          </td>
        </tr>
</table>
<p>
        </p>
<div>
        I'm using smeserver-affa-3.2.2.2-0.noarch.rpm

affa --send-key JOB_NAME 
does not take the remote ssh port into account.

I modified /sbin/affa line 2351 on my backup machine in the sendKeys()
subroutine and added 
 -p $job{'sshPort'} 

This fixed the issue.
        </div>

      <span>You are receiving this mail because:</span>

      <ul>
<li>You are the QA Contact for the bug.</li>
      </ul>
</div>
bugzilla-daemon | 7 Apr 05:27 2015

[Bug 8901] mod_deflate logs need to logrotate

Please DO NOT REPLY to this mail or send email to the developers about this bug.

Please follow-up to Bugzilla via Bug 8901.

Have you checked the Frequently Asked Questions (FAQ)?

Please also take the time to read "How to Report Bugs Effectively"
Bug ID Summary Classification Product Version Hardware OS Status Severity Priority Component Assignee Reporter QA Contact Depends on
8901
mod_deflate logs need to logrotate
Contribs
SME Contribs
9.0
---
---
CONFIRMED
normal
P3
smeserver-mod_deflate
mastersleepy <at> vanhees.cc
tests <at> pialasse.com
contribteam <at> lists.contribs.org
8900

+++ This bug was initially created as a clone of Bug #8900 +++ I have a server with pretty much traffic, here what I have after one year: -rw-r--r-- 1 root root 12G avril 6 23:20 deflate_log would be great to update the httpd template in order to logrotate it the same way acces_log is. then the server will handle oldish log to dispose it.
You are receiving this mail because:
  • You are the QA Contact for the bug.
<div>
Please DO NOT REPLY to this mail or send email to the developers about this bug.<br><br>
Please follow-up to Bugzilla via <a class="bz_bug_link 
          bz_status_CONFIRMED " title="CONFIRMED - mod_deflate logs need to logrotate" href="http://bugs.contribs.org/show_bug.cgi?id=8901">Bug 8901</a>.<br><br>
Have you checked the <a href="http://wiki.contribs.org/SME_Server:Documentation:FAQ">Frequently Asked Questions (FAQ)</a>?<br><br>
Please also take the time to read "<a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">How to Report Bugs Effectively</a>"<br><table border="1" cellspacing="0" cellpadding="8">
<tr>Bug ID
          <td>
<a class="bz_bug_link 
          bz_status_CONFIRMED " title="CONFIRMED - mod_deflate logs need to logrotate" href="http://bugs.contribs.org/show_bug.cgi?id=8901">8901</a>
          </td>
        </tr>
<tr>Summary
          <td>mod_deflate logs need to logrotate
          </td>
        </tr>
<tr>Classification
          <td>Contribs
          </td>
        </tr>
<tr>Product
          <td>SME Contribs
          </td>
        </tr>
<tr>Version
          <td>9.0
          </td>
        </tr>
<tr>Hardware
          <td>---
          </td>
        </tr>
<tr>OS
          <td>---
          </td>
        </tr>
<tr>Status
          <td>CONFIRMED
          </td>
        </tr>
<tr>Severity
          <td>normal
          </td>
        </tr>
<tr>Priority
          <td>P3
          </td>
        </tr>
<tr>Component
          <td>smeserver-mod_deflate
          </td>
        </tr>
<tr>Assignee
          <td>mastersleepy <at> vanhees.cc
          </td>
        </tr>
<tr>Reporter
          <td>tests <at> pialasse.com
          </td>
        </tr>
<tr>QA Contact
          <td>contribteam <at> lists.contribs.org
          </td>
        </tr>
<tr>Depends on
          <td>8900
          </td>
        </tr>
</table>
<p>
        </p>
<div>
        +++ This bug was initially created as a clone of <a class="bz_bug_link 
          bz_status_CONFIRMED " title="CONFIRMED - mod_deflate logs need to logrotate" href="show_bug.cgi?id=8900">Bug #8900</a> +++

I have a server with pretty much traffic, here what I have after one year:

-rw-r--r-- 1 root root   12G avril  6 23:20 deflate_log

would be great to update the httpd template in order to logrotate it the same
way acces_log is. 
then the server will handle oldish log to dispose it.
        </div>

      <span>You are receiving this mail because:</span>

      <ul>
<li>You are the QA Contact for the bug.</li>
      </ul>
</div>
bugzilla-daemon | 7 Apr 05:26 2015

[Bug 8900] mod_deflate logs need to logrotate

Please DO NOT REPLY to this mail or send email to the developers about this bug.

Please follow-up to Bugzilla via Bug 8900.

Have you checked the Frequently Asked Questions (FAQ)?

Please also take the time to read "How to Report Bugs Effectively"
Bug ID Summary Classification Product Version Hardware OS Status Severity Priority Component Assignee Reporter QA Contact
8900
mod_deflate logs need to logrotate
Contribs
SME Contribs
8.1
---
---
CONFIRMED
normal
P3
smeserver-mod_deflate
mastersleepy <at> vanhees.cc
tests <at> pialasse.com
contribteam <at> lists.contribs.org

I have a server with pretty much traffic, here what I have after one year: -rw-r--r-- 1 root root 12G avril 6 23:20 deflate_log would be great to update the httpd template in order to logrotate it the same way acces_log is. then the server will handle oldish log to dispose it.
You are receiving this mail because:
  • You are the QA Contact for the bug.
<div>
Please DO NOT REPLY to this mail or send email to the developers about this bug.<br><br>
Please follow-up to Bugzilla via <a class="bz_bug_link 
          bz_status_CONFIRMED " title="CONFIRMED - mod_deflate logs need to logrotate" href="http://bugs.contribs.org/show_bug.cgi?id=8900">Bug 8900</a>.<br><br>
Have you checked the <a href="http://wiki.contribs.org/SME_Server:Documentation:FAQ">Frequently Asked Questions (FAQ)</a>?<br><br>
Please also take the time to read "<a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">How to Report Bugs Effectively</a>"<br><table border="1" cellspacing="0" cellpadding="8">
<tr>Bug ID
          <td>
<a class="bz_bug_link 
          bz_status_CONFIRMED " title="CONFIRMED - mod_deflate logs need to logrotate" href="http://bugs.contribs.org/show_bug.cgi?id=8900">8900</a>
          </td>
        </tr>
<tr>Summary
          <td>mod_deflate logs need to logrotate
          </td>
        </tr>
<tr>Classification
          <td>Contribs
          </td>
        </tr>
<tr>Product
          <td>SME Contribs
          </td>
        </tr>
<tr>Version
          <td>8.1
          </td>
        </tr>
<tr>Hardware
          <td>---
          </td>
        </tr>
<tr>OS
          <td>---
          </td>
        </tr>
<tr>Status
          <td>CONFIRMED
          </td>
        </tr>
<tr>Severity
          <td>normal
          </td>
        </tr>
<tr>Priority
          <td>P3
          </td>
        </tr>
<tr>Component
          <td>smeserver-mod_deflate
          </td>
        </tr>
<tr>Assignee
          <td>mastersleepy <at> vanhees.cc
          </td>
        </tr>
<tr>Reporter
          <td>tests <at> pialasse.com
          </td>
        </tr>
<tr>QA Contact
          <td>contribteam <at> lists.contribs.org
          </td>
        </tr>
</table>
<p>
        </p>
<div>
        I have a server with pretty much traffic, here what I have after one year:

-rw-r--r-- 1 root root   12G avril  6 23:20 deflate_log

would be great to update the httpd template in order to logrotate it the same
way acces_log is. 
then the server will handle oldish log to dispose it.
        </div>

      <span>You are receiving this mail because:</span>

      <ul>
<li>You are the QA Contact for the bug.</li>
      </ul>
</div>
bugzilla-daemon | 7 Apr 00:37 2015

[Bug 8899] Apache Authentication fails on 9.1 beta

Please DO NOT REPLY to this mail or send email to the developers about this bug.

Please follow-up to Bugzilla via Bug 8899.

Have you checked the Frequently Asked Questions (FAQ)?

Please also take the time to read "How to Report Bugs Effectively"
Bug ID Summary Classification Product Version Hardware OS Status Severity Priority Component Assignee Reporter QA Contact
8899
Apache Authentication fails on 9.1 beta
Contribs
SME Contribs
9beta
---
---
UNCONFIRMED
normal
P3
smeserver-ajaxterm
mweinber <at> neddix.de
si.blakely <at> googlemail.com
contribteam <at> lists.contribs.org

Installed ajaxterm on to 9.1 beta Authentication appears to work but loading generates a 500 Application error Modified Apache template to suit Apache 2.2 /etc/e-smith/templates/etc/httpd/conf/httpd.conf/VirtualHosts/26ajaxterm { if ($port eq "443") { # 64 or i386 my $fileauth = -f "/usr/lib64/httpd/modules/pwauth" ? "/usr/lib64/httpd/modules/pwauth" : "/usr/lib/httpd/modules/pwauth"; $port=$Ajaxterm{servicePort}||8022; $users=$Ajaxterm{basicAuthUsers}||'admin'; $webalias=$Ajaxterm{webAlias}||'ajaxterm'; $OUT .= " # Ajaxterm\n"; $OUT .= " ProxyPass /$webalias/ http://127.0.0.1:$port/\n"; $OUT .= " ProxyPassReverse /$webalias/ http://127.0.0.1:$port/\n"; $OUT .= " DefineExternalAuth pwauth pipe /usr/bin/pwauth\n"; $OUT .= " <Location /$webalias>\n"; $OUT .= " order deny,allow\n"; $OUT .= " deny from all\n"; $OUT .= " allow from all\n"; $OUT .= " AuthName \"$webalias\"\n"; $OUT .= " AuthType Basic\n"; $OUT .= " AuthBasicProvider external\n"; $OUT .= " AuthExternal pwauth\n"; $OUT .= " require user $users\n"; $OUT .= " Satisfy all\n"; $OUT .= " </Location>\n"; } }
You are receiving this mail because:
  • You are the QA Contact for the bug.
<div>
Please DO NOT REPLY to this mail or send email to the developers about this bug.<br><br>
Please follow-up to Bugzilla via <a class="bz_bug_link 
          bz_status_UNCONFIRMED " title="UNCONFIRMED - Apache Authentication fails on 9.1 beta" href="http://bugs.contribs.org/show_bug.cgi?id=8899">Bug 8899</a>.<br><br>
Have you checked the <a href="http://wiki.contribs.org/SME_Server:Documentation:FAQ">Frequently Asked Questions (FAQ)</a>?<br><br>
Please also take the time to read "<a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">How to Report Bugs Effectively</a>"<br><table border="1" cellspacing="0" cellpadding="8">
<tr>Bug ID
          <td>
<a class="bz_bug_link 
          bz_status_UNCONFIRMED " title="UNCONFIRMED - Apache Authentication fails on 9.1 beta" href="http://bugs.contribs.org/show_bug.cgi?id=8899">8899</a>
          </td>
        </tr>
<tr>Summary
          <td>Apache Authentication fails on 9.1 beta
          </td>
        </tr>
<tr>Classification
          <td>Contribs
          </td>
        </tr>
<tr>Product
          <td>SME Contribs
          </td>
        </tr>
<tr>Version
          <td>9beta
          </td>
        </tr>
<tr>Hardware
          <td>---
          </td>
        </tr>
<tr>OS
          <td>---
          </td>
        </tr>
<tr>Status
          <td>UNCONFIRMED
          </td>
        </tr>
<tr>Severity
          <td>normal
          </td>
        </tr>
<tr>Priority
          <td>P3
          </td>
        </tr>
<tr>Component
          <td>smeserver-ajaxterm
          </td>
        </tr>
<tr>Assignee
          <td>mweinber <at> neddix.de
          </td>
        </tr>
<tr>Reporter
          <td>si.blakely <at> googlemail.com
          </td>
        </tr>
<tr>QA Contact
          <td>contribteam <at> lists.contribs.org
          </td>
        </tr>
</table>
<p>
        </p>
<div>
        Installed ajaxterm on to 9.1 beta 
Authentication appears to work but loading generates a 500 Application error

Modified Apache template to suit Apache 2.2
/etc/e-smith/templates/etc/httpd/conf/httpd.conf/VirtualHosts/26ajaxterm

{
if ($port eq "443")
    {
    # 64 or i386
    my $fileauth = -f "/usr/lib64/httpd/modules/pwauth" ?
"/usr/lib64/httpd/modules/pwauth" : "/usr/lib/httpd/modules/pwauth";

    $port=$Ajaxterm{servicePort}||8022;
    $users=$Ajaxterm{basicAuthUsers}||'admin';
    $webalias=$Ajaxterm{webAlias}||'ajaxterm';
    $OUT .= "    # Ajaxterm\n";
    $OUT .= "    ProxyPass /$webalias/ <a href="http://127.0.0.1:%24port/%5Cn">http://127.0.0.1:$port/\n</a>";
    $OUT .= "    ProxyPassReverse /$webalias/ <a href="http://127.0.0.1:%24port/%5Cn">http://127.0.0.1:$port/\n</a>";
    $OUT .= "    DefineExternalAuth pwauth pipe /usr/bin/pwauth\n";  
    $OUT .= "    &lt;Location /$webalias&gt;\n";
    $OUT .= "        order deny,allow\n";
    $OUT .= "        deny from all\n";
    $OUT .= "        allow from all\n";
    $OUT .= "        AuthName \"$webalias\"\n";
    $OUT .= "        AuthType Basic\n";
    $OUT .= "        AuthBasicProvider external\n";
    $OUT .= "        AuthExternal pwauth\n";
    $OUT .= "        require user $users\n";
    $OUT .= "        Satisfy all\n";
    $OUT .= "    &lt;/Location&gt;\n";
    }
}
        </div>

      <span>You are receiving this mail because:</span>

      <ul>
<li>You are the QA Contact for the bug.</li>
      </ul>
</div>
bugzilla-daemon | 31 Mar 05:30 2015

[Bug 8894] epel regex does not work with SME

Please DO NOT REPLY to this mail or send email to the developers about this bug.

Please follow-up to Bugzilla via Bug 8894.

Have you checked the Frequently Asked Questions (FAQ)?

Please also take the time to read "How to Report Bugs Effectively"
Bug ID Summary Classification Product Version Hardware OS Status Severity Priority Component Assignee Reporter QA Contact
8894
epel regex does not work with SME
Contribs
SME Contribs
9.0
---
---
CONFIRMED
normal
P3
smeserver-denyhosts
tests <at> pialasse.com
tests <at> pialasse.com
contribteam <at> lists.contribs.org

the most update package has introduced best practice regex to avoid that log injection permit to add new entries. However, the trailing $ to foce the end of string make denyhost fail in SME. we can add the regex in the conf file in order to make it work.
You are receiving this mail because:
  • You are the QA Contact for the bug.
<div>
Please DO NOT REPLY to this mail or send email to the developers about this bug.<br><br>
Please follow-up to Bugzilla via <a class="bz_bug_link 
          bz_status_CONFIRMED " title="CONFIRMED - epel regex does not work with SME" href="http://bugs.contribs.org/show_bug.cgi?id=8894">Bug 8894</a>.<br><br>
Have you checked the <a href="http://wiki.contribs.org/SME_Server:Documentation:FAQ">Frequently Asked Questions (FAQ)</a>?<br><br>
Please also take the time to read "<a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">How to Report Bugs Effectively</a>"<br><table border="1" cellspacing="0" cellpadding="8">
<tr>Bug ID
          <td>
<a class="bz_bug_link 
          bz_status_CONFIRMED " title="CONFIRMED - epel regex does not work with SME" href="http://bugs.contribs.org/show_bug.cgi?id=8894">8894</a>
          </td>
        </tr>
<tr>Summary
          <td>epel regex does not work with SME
          </td>
        </tr>
<tr>Classification
          <td>Contribs
          </td>
        </tr>
<tr>Product
          <td>SME Contribs
          </td>
        </tr>
<tr>Version
          <td>9.0
          </td>
        </tr>
<tr>Hardware
          <td>---
          </td>
        </tr>
<tr>OS
          <td>---
          </td>
        </tr>
<tr>Status
          <td>CONFIRMED
          </td>
        </tr>
<tr>Severity
          <td>normal
          </td>
        </tr>
<tr>Priority
          <td>P3
          </td>
        </tr>
<tr>Component
          <td>smeserver-denyhosts
          </td>
        </tr>
<tr>Assignee
          <td>tests <at> pialasse.com
          </td>
        </tr>
<tr>Reporter
          <td>tests <at> pialasse.com
          </td>
        </tr>
<tr>QA Contact
          <td>contribteam <at> lists.contribs.org
          </td>
        </tr>
</table>
<p>
        </p>
<div>
        the most update package has introduced best practice regex to avoid that log
injection permit to add new entries.

However, the trailing $ to foce the end of string make denyhost fail in SME.

we can add the regex in the conf file in order to make it work.
        </div>

      <span>You are receiving this mail because:</span>

      <ul>
<li>You are the QA Contact for the bug.</li>
      </ul>
</div>
bugzilla-daemon | 31 Mar 00:29 2015

[Bug 8892] /etc/denyhosts.conf vs /etc/denyhosts/denyhosts.cfg

Please DO NOT REPLY to this mail or send email to the developers about this bug.

Please follow-up to Bugzilla via Bug 8892.

Have you checked the Frequently Asked Questions (FAQ)?

Please also take the time to read "How to Report Bugs Effectively"
Bug ID Summary Classification Product Version Hardware OS Status Severity Priority Component Assignee Reporter QA Contact
8892
/etc/denyhosts.conf vs /etc/denyhosts/denyhosts.cfg
Contribs
SME Contribs
9.0
---
---
CONFIRMED
normal
P3
smeserver-denyhosts
tests <at> pialasse.com
tests <at> pialasse.com
contribteam <at> lists.contribs.org

pkg from repoforge # rpm -qa |grep deny denyhosts-2.6-5.el6.rf.noarch smeserver-denyhosts-2.9-1.el6.sme.noarch will use .cfg file instead you should use epel package to stick to the current conf path. Further more it is more recent.
You are receiving this mail because:
  • You are the QA Contact for the bug.
<div>
Please DO NOT REPLY to this mail or send email to the developers about this bug.<br><br>
Please follow-up to Bugzilla via <a class="bz_bug_link 
          bz_status_CONFIRMED " title="CONFIRMED - /etc/denyhosts.conf vs /etc/denyhosts/denyhosts.cfg" href="http://bugs.contribs.org/show_bug.cgi?id=8892">Bug 8892</a>.<br><br>
Have you checked the <a href="http://wiki.contribs.org/SME_Server:Documentation:FAQ">Frequently Asked Questions (FAQ)</a>?<br><br>
Please also take the time to read "<a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">How to Report Bugs Effectively</a>"<br><table border="1" cellspacing="0" cellpadding="8">
<tr>Bug ID
          <td>
<a class="bz_bug_link 
          bz_status_CONFIRMED " title="CONFIRMED - /etc/denyhosts.conf vs /etc/denyhosts/denyhosts.cfg" href="http://bugs.contribs.org/show_bug.cgi?id=8892">8892</a>
          </td>
        </tr>
<tr>Summary
          <td>/etc/denyhosts.conf vs  /etc/denyhosts/denyhosts.cfg
          </td>
        </tr>
<tr>Classification
          <td>Contribs
          </td>
        </tr>
<tr>Product
          <td>SME Contribs
          </td>
        </tr>
<tr>Version
          <td>9.0
          </td>
        </tr>
<tr>Hardware
          <td>---
          </td>
        </tr>
<tr>OS
          <td>---
          </td>
        </tr>
<tr>Status
          <td>CONFIRMED
          </td>
        </tr>
<tr>Severity
          <td>normal
          </td>
        </tr>
<tr>Priority
          <td>P3
          </td>
        </tr>
<tr>Component
          <td>smeserver-denyhosts
          </td>
        </tr>
<tr>Assignee
          <td>tests <at> pialasse.com
          </td>
        </tr>
<tr>Reporter
          <td>tests <at> pialasse.com
          </td>
        </tr>
<tr>QA Contact
          <td>contribteam <at> lists.contribs.org
          </td>
        </tr>
</table>
<p>
        </p>
<div>
        pkg from repoforge
# rpm -qa |grep deny
denyhosts-2.6-5.el6.rf.noarch
smeserver-denyhosts-2.9-1.el6.sme.noarch

will 
 use .cfg file

instead you should use epel package to stick to the current conf path. Further
more it is more recent.
        </div>

      <span>You are receiving this mail because:</span>

      <ul>
<li>You are the QA Contact for the bug.</li>
      </ul>
</div>
bugzilla-daemon | 29 Mar 19:26 2015

[Bug 8888] first import to sme9 tree [smeserver-qmHandle]

Please DO NOT REPLY to this mail or send email to the developers about this bug.

Please follow-up to Bugzilla via Bug 8888.

Have you checked the Frequently Asked Questions (FAQ)?

Please also take the time to read "How to Report Bugs Effectively"
Bug ID Summary Classification Product Version Hardware OS Status Severity Priority Component Assignee Reporter QA Contact
8888
first import to sme9 tree [smeserver-qmHandle]
Contribs
SME Contribs
9.0
---
---
CONFIRMED
normal
P3
smeserver-qmHandle
tests <at> pialasse.com
tests <at> pialasse.com
contribteam <at> lists.contribs.org

just built a fresh import of qmHandle to the smedev repo need to be tested
You are receiving this mail because:
  • You are the QA Contact for the bug.
<div>
Please DO NOT REPLY to this mail or send email to the developers about this bug.<br><br>
Please follow-up to Bugzilla via <a class="bz_bug_link 
          bz_status_CONFIRMED " title="CONFIRMED - first import to sme9 tree [smeserver-qmHandle]" href="http://bugs.contribs.org/show_bug.cgi?id=8888">Bug 8888</a>.<br><br>
Have you checked the <a href="http://wiki.contribs.org/SME_Server:Documentation:FAQ">Frequently Asked Questions (FAQ)</a>?<br><br>
Please also take the time to read "<a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">How to Report Bugs Effectively</a>"<br><table border="1" cellspacing="0" cellpadding="8">
<tr>Bug ID
          <td>
<a class="bz_bug_link 
          bz_status_CONFIRMED " title="CONFIRMED - first import to sme9 tree [smeserver-qmHandle]" href="http://bugs.contribs.org/show_bug.cgi?id=8888">8888</a>
          </td>
        </tr>
<tr>Summary
          <td>first import to sme9 tree [smeserver-qmHandle]
          </td>
        </tr>
<tr>Classification
          <td>Contribs
          </td>
        </tr>
<tr>Product
          <td>SME Contribs
          </td>
        </tr>
<tr>Version
          <td>9.0
          </td>
        </tr>
<tr>Hardware
          <td>---
          </td>
        </tr>
<tr>OS
          <td>---
          </td>
        </tr>
<tr>Status
          <td>CONFIRMED
          </td>
        </tr>
<tr>Severity
          <td>normal
          </td>
        </tr>
<tr>Priority
          <td>P3
          </td>
        </tr>
<tr>Component
          <td>smeserver-qmHandle
          </td>
        </tr>
<tr>Assignee
          <td>tests <at> pialasse.com
          </td>
        </tr>
<tr>Reporter
          <td>tests <at> pialasse.com
          </td>
        </tr>
<tr>QA Contact
          <td>contribteam <at> lists.contribs.org
          </td>
        </tr>
</table>
<p>
        </p>
<div>
        just built a  fresh import of qmHandle to the smedev repo

need to be tested
        </div>

      <span>You are receiving this mail because:</span>

      <ul>
<li>You are the QA Contact for the bug.</li>
      </ul>
</div>

Gmane