View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001463 | Anope Development (1.9.x series) | Modules System | public | 2012-12-25 18:10 | 2012-12-25 23:47 |
| Reporter | CuttingEdge | Assigned To | Adam | ||
| Priority | high | Severity | crash | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Summary | 0001463: Crash on unload and reload of OperServ DNS module. | ||||
| Description | Services crashes/disconnects after module reload and commands sent to add zones/servers/IP addresses to OperServ DNS module. | ||||
| Steps To Reproduce | 1) Unload os_dns. 2) Reload os_dns. 3) Readd servers to configuration (they are not displayed, or shown after the reload). 4) Anope crashes, disconnects from network during a database save: [Dec 25 17:50:00 2012] Saving databases [Dec 25 17:50:00 2012] bs_main: Running bandata purger [Dec 25 17:50:00 2012] DB_FLATFILE: Error saving databases: Unable to write database data/anope.db [Dec 25 17:50:00 2012] Terminating, reason unknown | ||||
| Additional Information | I have a sneaky suspicion that the settings are not reloaded (from the database) on module reload. The module is probably trying to write settings that exist? Using latest Anope 1.9.x GIT. | ||||
| Tags | No tags attached. | ||||
|
|
fixed in 556a4375e226760169150179b5bcaa659aaf055e and 392b591d09509ae788f59b1b63a947ed7d8ad562 |
|
|
Something else to note, is that the OperServ DNS module does not write to MySQL databases if the database type is of MySQL (everything else does). The above crash was done on a flatfile database though. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-12-25 18:10 | CuttingEdge | New Issue | |
| 2012-12-25 18:11 | CuttingEdge | Note Added: 0006310 | |
| 2012-12-25 23:47 | Adam | Note Added: 0006311 | |
| 2012-12-25 23:47 | Adam | Status | new => resolved |
| 2012-12-25 23:47 | Adam | Resolution | open => fixed |
| 2012-12-25 23:47 | Adam | Assigned To | => Adam |
