Line 2: |
Line 2: |
| There are still some bugs in this RPM... Help us to fix them! | | There are still some bugs in this RPM... Help us to fix them! |
| ==ipdiscover bug== | | ==ipdiscover bug== |
− | We need to confirm that ipdiscover works when the smeserver is the forced client.
| + | ===ipdiscover on SME=== |
| + | IpDiscover is not working on SME. Please use another agent to ipdiscover your networks at the moment. |
| | | |
− | I Tried the following: | + | I've opened a [http://forums.ocsinventory-ng.org/viewtopic.php?pid=5684#p5684 thread] on OCS forum. |
− | ipdiscover eth0 10
| |
− | {{Note box|''Usage : ipdiscover [iface name] [latency in ms]''}}
| |
| | | |
− | Here's what I got on my server:
| + | Let's hope the next version will come out soon! |
− | <IPDISCOVER>
| + | ===ipdiscover-util.pl=== |
− | <H><I>192.168.0.100</I><M>00:xx:xx:xx:xx:xx</M><N>pc-00100.mydomain.com</N></H>
| + | This script used by the web interface do not seem to work too. |
− | <H><I>192.168.0.253</I><M>00:xx:xx:xx:xx:xx</M><N>pc-00253.mydomain.com</N></H>
| |
− | <H><I>192.168.0.254</I><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...
| + | First thing to do is to change the password in this file... |
| + | ... |
| + | my $dbhost = 'localhost'; |
| + | my $dbuser = 'ocs'; |
| + | my $dbpwd = 'ocs'; <== |
| + | my $db = 'ocsweb'; |
| + | my $dbp = '3306'; |
| + | The password should be dynamical as this is a perl script. We need to use esmith::ConfigDB or something else to retrieve this value... I was unable to handle that. |
| | | |
− | Cool34000
| + | Also a problem, the script cannot be executed. I try to add script handler for .pl but it didn't worked... Not sure about how this is working, if someone can help, please do! |
− | ----
| |
− | ==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 | | Cool34000 |
| ---- | | ---- |
| | | |
− | add a package, deploy > activate > click on the red X
| + | ==www/ocs/install.php bugs== |
− | ERROR: Can't delete directory /opt/inventory/ocs/download/1194511477
| + | A problem was found in the default imported database. This ends with some ''alter'' errors. This can be fixed by refreshing the web page. |
| | | |
− | I have documented that you can ignore the error, maybe i should say if you see the error you can ignore? | + | I took a look on ocsweb database with phpmyadmin before and after using install.php |
| | | |
− | stephen
| + | I noticed that a lot of tables' ''engine type'' were ''MyISAM'' and after using install.php their type was ''InnoDB''! |
− | ----
| |
− | =future RPM=
| |
− | What will be fixed in next RPM release...
| |
− | ==upload size limit==
| |
− | Max allowed packet value is locked at 10M by default on SME.
| |
− | Let's delete the mysql custom-template in the future RPM!
| |
| | | |
− | We can modify this value to only affect the ocs directory.
| + | So I tried to export a new database (this time with extended parameters), but this new database don't import in ocsweb database: it ends with errors trying to create the 1st table! |
− |
| |
− | Add the following lines to Apache template:
| |
− | <Directory /opt/inventory/ocs/ocsreports>
| |
− | ..
| |
− | php_admin_value post_max_size $ocs{'MaxUpload'}
| |
− | php_admin_value upload_max_filesize $ocs{'MaxUpload'}
| |
− | Apply changes:
| |
− | config setprop ocs MaxUpload xxM
| |
− | expand-template /etc/httpd/conf/httpd.conf
| |
− | /etc/init.d/httpd-e-smith condrestart
| |
− | Default value: 10M
| |
| | | |
− | ==aliases==
| + | Help needed! |
− | Future RPM will allow to add aliases using 'URL' value to ocs and glpi
| |
− | {
| |
− | if (exists $foo{'URL'})
| |
− | { $OUT .= "Alias /$foo{'URL'} /opt/foo\n"; }
| |
− | }
| |
| | | |
− | ==RPM is not a chatroom==
| |
− | Less chat in the install output, just say look at the renamed wiki page
| |
− |
| |
− | ==events==
| |
− | Don't use signal-event my-own-event: just give all the commands, or use an existing one, we could use domain-modify
| |
− |
| |
− | Stefen
| |
− | ----
| |
− | Here's the future createlinks perl script:
| |
− | #!/usr/bin/perl -w
| |
− | use esmith::Build::CreateLinks qw(:all);
| |
− |
| |
− | # Templates to adjust
| |
− | templates2events("/etc/e-smith/sql/init/80ocs_mysql.sql", qw(domain-modify post-upgrade ));
| |
− | templates2events("/etc/e-smith/sql/init/82glpi_mysql.sql", qw(domain-modify post-upgrade ));
| |
− | templates2events("/etc/e-smith/sql/init/84ocs-glpi.sql", qw(domain-modify post-upgrade ));
| |
− | templates2events("/etc/ocsinventory-agent/ocsinv.conf", qw(domain-modify post-upgrade ));
| |
− | templates2events("/opt/inventory/glpi/config/config_db.php", qw(domain-modify post-upgrade ));
| |
− | templates2events("/opt/inventory/ocs/ocsreports/dbconfig.inc.php", qw(domain-modify post-upgrade ));
| |
− | # Services to restart
| |
− | safe_symlink("start", "root/etc/e-smith/events/domain-modify/services2adjust/mysql.init");
| |
− | Apache is already expanded and restarted by event ''domain-modify'' so I removed these useless lines... Events are also available when calling a ''post-upgrade''. I based this on how SME handles webmail and also what I've found in other SPRMs...
| |
− |
| |
− |
| |
− | How I handle SME integration:
| |
− | 80ocs_mysql.sql => create/update ocs database+user+password
| |
− | 82glpi_mysql.sql => create/update glpi database+user+password
| |
− | 84ocs-glpi.sql => apply ocs' password in glpi database
| |
− | ocsinv.conf => apply Agent config
| |
− | config_db.php => MySQL DB passwords
| |
− | dbconfig.inc.php => MySQL DB passwords
| |
− | {{Warning box|These templates allow to restore the good password when using www/ocs/install.php (used for web interface updates!!!)}}
| |
− | {{Note box|These templates also ensures that if ocs password changes, it will be updated in glpi MySQL database!!!}}
| |
− | {{Note box|These templates are working for RPM install, RPM updates and everyday use :-)}}
| |
| Cool34000 | | Cool34000 |
| ---- | | ---- |
| | | |
− | ==save bandwidth== | + | =wiki page= |
− | Create a separate RPM with the ''ocsagent.exe'' and ''guide.pdf'' and make it a dependency of the main RPM...
| |
| | | |
− | Or maybe not?
| |
| | | |
− | => files deleted in the tarball, this is 1.5MB + 6MB
| |
| | | |
− | => ocsagent.exe needs to be installed anyway with www/ocs/install.php | + | ==5.3.2 Deployment menu== |
| | | |
− | People should download latest client and put ocsagent.exe in www/ocs/files
| + | there must be a lot of ways this could be used, |
| + | why make everyone think of them themselves when it could be spelled out |
| | | |
− | Will document this later
| + | this could be a new page, [[:Application deployment]] |
| | | |
− | => figured out why the guide.pdf is needed: there a link to it the web interface...
| + | this could include other ways to deploy, eg using netlogon.bat |
| | | |
− | People can download this file... Or not, let's warn that the help page won't be accessible in OCS!
| + | others can work on this cool34000 has done enough |
− | | |
− | I think there is no need to put them as requires. I can put the guide.pdf in my folder and give the link in the wiki.
| |
− | | |
− | ==MySQL init scripts ==
| |
− | /etc/e-smith/sql/init/* should only be used one to create the db table, then it is deleted
| |
− | httpd.conf and php.ini are in standard events (and are we still changing php.ini?)
| |
− | which only leaves three fragments to document in the rare case that something changes
| |
| | | |
| Stefen | | Stefen |
| ---- | | ---- |
− | Yes, all that goes in /etc/e-smith/sql/init/ is dropped after a successful importation. I know that, I use it this way:
| + | Here's the way I've always used OCS... First I import the standard ''ocsagent.exe'' in MySQL. |
− | *3 templates to dynamically create the DB+User+Password and change OCS' password in GLPI' database. These templates are harmless if re-expanded...
| |
− | | |
− | *2 databases (one for ocs, one for glpi). They are imported ONLY ON NEW INSTALL. These 2 databases are dropped once imported (no need to keep them!)... It also allows me to import the right GLPI database according to ''$LANG''
| |
− | | |
− | So when the RPM runs:
| |
− | * 3 files loaded on RPM updates
| |
− | * 5 files loaded on RPM install
| |
− | Take a look on their name when all 5 files are put in /etc/e-smith/sql/init/ once expanded
| |
− | | |
− | Cool3400
| |
− | ----
| |
| | | |
| + | I don't like to install a service when it's not needed, so I use the standalone executable. I also don't use OCS deployment feature (I'm using GPOs for that) |
| | | |
− | ==dependencies==
| + | It is so fast to use against the need of installing the Agent: put OcsLogon.exe in a share folder and simply launch it with a one command line batch script each time a session is opened. |
| + | @echo off |
| + | \\server\share\mydomain.com.exe /np /debug /tag:my_tag |
| + | That's all! |
| | | |
− | change the install method to install the perl dependencies that are available from existing repos.
| + | Of course, more can be done... |
| | | |
− | Then you can reduce the number of perl rpms in your download the less you are responsible for the better
| + | *Install the Agent silently in a script |
| + | *Use GPOs (deploy, install, update) |
| + | *Create your own ''ocsagent.exe'' |
| + | People need to read the guide! It's well documented. |
| | | |
− | yum localinstall smeserver-inventory-tools* --enablerepo=?
| + | If someone can take some time to document that, it would be nice! |
| | | |
− | stephen
| + | Cool34000 |
| ---- | | ---- |
| | | |
| + | ==glpi== |
| | | |
− | | + | someone who uses this may like to add some more information on how to use it, some link to more docs at least |
− | ==new accounts==
| |
− | 2 'url' accounts types will be created for ocs:
| |
− | root/etc/e-smith/db/accounts/defaults/ocsinterface | |
− | root/etc/e-smith/db/accounts/defaults/ocsinventory
| |
− | These virtual locations are used by ocs server-side.
| |