Difference between revisions of "Talk:OCS Inventory Tools"

From SME Server
Jump to navigationJump to search
Line 41: Line 41:
 
==Upload size limit bug==
 
==Upload size limit bug==
 
Must document that on the Wiki:
 
Must document that on the Wiki:
  Max allowed packet value is set to 50M with a custom-template by the RPM.
+
  Max allowed packet value is set to 10M.
This should allow to upload comfortable package size.
 
  
I didn't test to upload such file size to confirm this is working as expected...
 
=> can we really upload files greater than 10MB?
 
=> if yes, what happens at 50.1MB (just curious lol)
 
 
  => impact of setting such large value on the server?
 
  => impact of setting such large value on the server?
=> create a DB entry in ocs to set this value and improve the custom-template to allow dynamic changes? This can't be bad!
 
 
  => lower this value maybe?
 
  => lower this value maybe?
  
Cool34000
+
No need to create a custom template: DB values already exist for this! They are hidden in php.ini templates ''40DataHandling'' and ''60FileUploads''
----
 
with ver -5, there is still a 10mb limit, below fixes, but having a db value would be better
 
  
<Directory /opt/inventory/ocs/ocsreports>
+
php Values can be changed with the following:
  # SSLRequireSSL on
+
  config setprop php UploadMaxFilesize 50M PostMaxSize 50M
  AddType application/x-httpd-php .php .php3 .phtml
+
  expand-template /etc/php.ini
  Options None
+
  signal-event ocsglpi-update
  Options +Indexes
 
  Options +Includes
 
  order deny,allow
 
  deny from all
 
  allow from xxxxxxxxxxxxxx
 
  php_admin_value open_basedir /opt/inventory/ocs:/tmp
 
  + php_admin_value post_max_size 40M
 
  + php_admin_value upload_max_filesize 40M
 
  </Directory>
 
  
+ php_admin_value upload_max_filesize $ocs{MaxUpload}  (untested)
+
Worked for me!
 
 
stephen
 
----
 
I was also testing this right now... Just figured out modifications to my.cnf are useless (still locked at 10M)
 
Got these info from www/ocs/install.php
 
WARNING: You will not be able to build any auto deployment package with size greater than 10M.
 
You must raise both post_max_size and upload_max_filesize in your php.ini to correct this.
 
 
WARNING: The user you typed does not seem to be root
 
If you encounter any problem with files insertion, try setting the global max_allowed_packet mysql value to at least 2M in your server config file.
 
 
 
I've tested these without success:
 
#--------------------------------------------------------------
 
# OCS Inventory Next Generation
 
#--------------------------------------------------------------
 
Alias /download /opt/inventory/ocs/download
 
Alias /ocs      /opt/inventory/ocs/ocsreports
 
{
 
    if (exists $ocs{'URL'})
 
      { $OUT .= "Alias  /$ocs{'URL'} /opt/inventory/ocs/ocsreports"; }
 
}
 
 
<Directory /opt/inventory/ocs/download>
 
  Options None
 
  Options +Indexes
 
  Options +Includes
 
  AllowOverride None
 
  order deny,allow
 
  deny from all
 
  allow from { $localAccess }
 
  php_admin_value open_basedir /opt/inventory/ocs/download:/tmp
 
  php_admin_value post_max_size { $ocs{PhpLimit} }M
 
  php_admin_value upload_max_filesize { $ocs{PhpLimit} }M
 
</Directory>
 
Values expand correctly, but I still get an error page...
 
 
 
Did it worked for you? I still can upload a 24MB file (-> getting an error
 
 
 
Should we directly modify php.ini with a custom-template? I saw defaut values set to 20M (post max size) and 10M (max upload filesize)
 
  
 
Cool34000
 
Cool34000

Revision as of 11:46, 8 November 2007

ipdiscover bug

We need to confirm that ipdiscover works when the smeserver is the forced client.

I Tried the following:

ipdiscover eth0 10
Important.png Note:
Usage : ipdiscover [iface name] [latency in ms]


Here's what I got on my server:

<IPDISCOVER>
<H>192.168.0.100<M>00:xx:xx:xx:xx:xx</M><N>pc-00100.mydomain.com</N></H>
<H>192.168.0.253<M>00:xx:xx:xx:xx:xx</M><N>pc-00253.mydomain.com</N></H>
<H>192.168.0.254<M>00:xx:xx:xx:xx:xx</M><N>pc-00254.mydomain.com</N></H>
</IPDISCOVER>

Sounds like it's working for me... But IpDiscover discovers nothing when launched by SME OCS' Agent. There must be a problem here!

Windows Agent don't have this problem...

Cool34000


deployment

deletion bug

When you delete a package, ocs complains, but it deletes the files anyway, document later

Stefen


The only way I was able to reproduce an error on package deletion is when I refreshed the page (as files were already removed, I got an error)

Could you be more clear on this bug? How did it happened?

Cool34000


add a package, deploy > activate > click on the red X

ERROR: Can't delete directory /opt/inventory/ocs/download/1194511477

I have documented that you can ignore the error, maybe i should say if you see the error you can ignore?

stephen


Upload size limit bug

Must document that on the Wiki:

Max allowed packet value is set to 10M.
=> impact of setting such large value on the server?
=> lower this value maybe?

No need to create a custom template: DB values already exist for this! They are hidden in php.ini templates 40DataHandling and 60FileUploads

php Values can be changed with the following:

config setprop php UploadMaxFilesize 50M PostMaxSize 50M
expand-template /etc/php.ini
signal-event ocsglpi-update

Worked for me!

Cool34000


glpi

a minor change, don't release an rpm just for this

/glpi is hard to remember

can we add a duplicate alias, eg /reports

or make a URL db setting so it is configurable

http://wiki.contribs.org/Web_Application_RPM#Webserver_templates

{
  if (exists $foo{'URL'})
  { $OUT .= "Alias  /$foo{'URL'}  /opt/foo\n"; }
}

Stefen


NP, I'll add this improvement in the next release. Do you want this for OCS too?

=> Is there a way to improve your code to test before using the alias that it will not override an existing one?

I will also set 'ocsinventory' and 'ocsinterface' as 'url' types to avoid using these virtual locations ;-) (forgot these ones!)

By the way, it's not so hard to remember: GLPI means Gestion Libre de Parc Informatique :-D

Very easy to remember... For a French guy!

Cool34000


ocs is ok, but maybe give it a URL db for completness,

as the fragment is last in httpd overwriting another value isn't a problem, the point is valid but the only thing that will happen in one of the local sites won't be visible

stephen