I'm currently trying to implement the Cable Modem stats Template ( http://docs.cacti.net/usertemplate:data ... em:generic) on my Cacti 0.8.7d installation.
I have verified the correct working of the perl script, and am now trying to import the enclosed two XML files. I have both tried the 'import by local file' aswell as the 'Import Template from Text' options and have tried that under FF3, FF2 and IE6, but nothing visibly happens when I press the save button on the Import Templates screen and nothing gets added to the templates sections.
The table on the templates overview (http://docs.cacti.net/templates) states this template is compatible with version 0.8.7d.
The cacti installation is on Fedora 11 thru the fedora cacti RPM. file_uploads = On and memory_limit = 32M in php.ini.
I've looked around in logfiles but am unable to find any errors.
Has anyone any idea what might be going wrong or give me some pointers where to look for clues?
Problem importing Cable Modem templates
Moderators: Developers, Moderators
Cacti 0.8.7e is the latest.
On the Import Templates screen, after you click Save, what happens?
Are you able to import ANY templates successfully? Look in the script forum for some popular ones...
On the Import Templates screen, after you click Save, what happens?
Are you able to import ANY templates successfully? Look in the script forum for some popular ones...
| Scripts: Monitor processes | RFC1213 MIB | DOCSIS Stats | Dell PowerEdge | Speedfan | APC UPS | DOCSIS CMTS | 3ware | Motorola Canopy |
| Guides: Windows Install | [HOWTO] Debug Windows NTFS permission problems |
| Tools: Windows All-in-one Installer |
I saw 0.8.7e is the latest but since the template version states 0.8.7d I thought it best to keep it on that version for now (unless there's a specific bug that is fixed that seems to be related?)BSOD2600 wrote:Cacti 0.8.7e is the latest.
On the Import Templates screen, after you click Save, what happens?
Are you able to import ANY templates successfully? Look in the script forum for some popular ones...
After I click save, nothing happens except for the filename or copied text disappearing from the input boxes on the import templates screen.
I have just imported a template from the script forum (tcp port) as you suggested. That seems to have worked. So I guess all cacti config stuff is in order for importing and the problem lies in the template files?
It's weird 'cause 0.8.7d is specifically mentioned at the download (http://docs.cacti.net/usertemplate:data ... em:generic)
Older templates are/should compatible with all newer versions of cacti but not backwards (e.g. template exported with cacti 0.8.7d CANNOT be imported into cacti 0.8.7c but CAN be imported to cacti 0.8.7e).grep wrote:I saw 0.8.7e is the latest but since the template version states 0.8.7d I thought it best to keep it on that version for now (unless there's a specific bug that is fixed that seems to be related?)
Enable the php error log (php.ini -- don't forget to restart the web service) and then look for any errors while you import the template.
| Scripts: Monitor processes | RFC1213 MIB | DOCSIS Stats | Dell PowerEdge | Speedfan | APC UPS | DOCSIS CMTS | 3ware | Motorola Canopy |
| Guides: Windows Install | [HOWTO] Debug Windows NTFS permission problems |
| Tools: Windows All-in-one Installer |
I have turned on the php error logging in php.ini:
error_reporting = E_ALL
display_errors = On
log_errors = On
error_log = php_error.log
but no errors are generated during the import attempts. Nothing gets written to the above mentioned error log, message log, cacti log or httpd error log.
I guess upgrading to 8e is the next step, though I have a hard time believing this will solve the problem.
error_reporting = E_ALL
display_errors = On
log_errors = On
error_log = php_error.log
but no errors are generated during the import attempts. Nothing gets written to the above mentioned error log, message log, cacti log or httpd error log.
I guess upgrading to 8e is the next step, though I have a hard time believing this will solve the problem.
I believe you need the full path for error_log, e.g. c:\php\php_error.log
If the hash version was an issue, cacti wouldn't let you import the template. http://docs.cacti.net/howto:determine_c ... te_version
If I have time later today, I'll try importing the template on a clean Cacti VMware install and see if I run into problems...
If the hash version was an issue, cacti wouldn't let you import the template. http://docs.cacti.net/howto:determine_c ... te_version
If I have time later today, I'll try importing the template on a clean Cacti VMware install and see if I run into problems...
| Scripts: Monitor processes | RFC1213 MIB | DOCSIS Stats | Dell PowerEdge | Speedfan | APC UPS | DOCSIS CMTS | 3ware | Motorola Canopy |
| Guides: Windows Install | [HOWTO] Debug Windows NTFS permission problems |
| Tools: Windows All-in-one Installer |
I've put a path before php error log, but still nothing was logged.
I have given up on importing the template and am recreating them manually now by looking at the XML code, and it seems to work nicely now (had some problems with the 'LAST cf' problem as described here, but luckily that topic also provided the solution to that problem).
Thanks to all who were thinking with me on this.
I have given up on importing the template and am recreating them manually now by looking at the XML code, and it seems to work nicely now (had some problems with the 'LAST cf' problem as described here, but luckily that topic also provided the solution to that problem).
Thanks to all who were thinking with me on this.
Who is online
Users browsing this forum: No registered users and 0 guests