| Summary | migration-scripts do not obey to proxy-settings |
| Queue | Horde Framework Packages |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | mrubinsk (at) horde (dot) org |
| Requester | cheese (at) nosuchhost (dot) net |
| Created | 12/07/2016 (3129 days ago) |
| Due | |
| Updated | 12/07/2016 (3129 days ago) |
| Assigned | |
| Resolved | 12/07/2016 (3129 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
Assigned to Michael Rubinsky
State ⇒ Resolved
Priority ⇒ 1. Low
been decommissioned - so the first migration is expected to fail. The
second migration is wrapped in a db transaction, which causes it to
take a long time to run. You are probably hitting a timeout.
Regardless, I just finished removing the migrations from that package
and replacing them with a standalone cli script
'horde-service-weather-metar-database that only needs to be run if you
are planning on making the metar weather block available.
Priority ⇒ 2. Medium
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Framework Packages
Summary ⇒ migration-scripts do not obey to proxy-settings
Type ⇒ Bug
State ⇒ Unconfirmed
$conf['http']['proxy']['proxy_host'] = "1.2.3.4";
but migration hangs during database-migration:
horde-db-migration:
...
[ INFO ] Current Horde_Service_Weather schema version: 1
Migrating to HordeServiceWeatherAirportsChange (2)
== 2 HordeServiceWeatherAirportsChange: migrating
=============================
== 2 HordeServiceWeatherAirportsChange: ERROR: Unable to populate
METAR database.
Unable to locate METAR data.
[ INFO ] Current Horde_SessionHandler schema version: 2
...
does not work through webpage, either.
yours
josef