<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Problems after upgrade]]></title><description><![CDATA[<p dir="auto">Hi Nicolas,</p>
<p dir="auto">I have updated to latest fop2 version to try fixing Chrome's issues that were getting people crazy here. As I use port eth1, I went inside the Makefile and added the -i eth1 to the reactivate command and was able to install it. I have also ran the FreePBX script to update the buttons as instructed by README file.</p>
<p dir="auto">I checked the two config files that were before compared to the new ones and I saw no major changes and then I restarted the fop2 service to get things on the new version. This was the first surprise, the service doesn't start up anymore using init.d script and I couldn't find logs to see what is going on.</p>
<p dir="auto">I started then using '/usr/local/fop2/fop2_server -i eth1 -d' and it started ok but then when I visit the page and all my panel is gone with only a NO BUTTONS green box and even going to FreePBX and re-applying all settings won't work.</p>
<p dir="auto">Before I had couple complaining users. Now I have all users unable to work. Can you please help?</p>
<p dir="auto">Thanks.</p>
]]></description><link>http://localhost:4567/topic/905/problems-after-upgrade</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 08:26:55 GMT</lastBuildDate><atom:link href="http://localhost:4567/topic/905.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 28 Sep 2011 14:34:21 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Problems after upgrade on Thu, 29 Sep 2011 11:56:22 GMT]]></title><description><![CDATA[<p dir="auto">You can edit the options file in /etc/sysconfig/fop2 to add whatever parameters necessary, as any other service in a redhat/centos box. That way you do not have to modify the init script itself, and an upgrade will not break your custom parameters.</p>
]]></description><link>http://localhost:4567/post/4017</link><guid isPermaLink="true">http://localhost:4567/post/4017</guid><dc:creator><![CDATA[nicolas]]></dc:creator><pubDate>Thu, 29 Sep 2011 11:56:22 GMT</pubDate></item><item><title><![CDATA[Reply to Problems after upgrade on Thu, 29 Sep 2011 02:45:26 GMT]]></title><description><![CDATA[<p dir="auto">Thanks! How about the service startup with eth1 on init.d script issue?</p>
]]></description><link>http://localhost:4567/post/4016</link><guid isPermaLink="true">http://localhost:4567/post/4016</guid><dc:creator><![CDATA[fagiani]]></dc:creator><pubDate>Thu, 29 Sep 2011 02:45:26 GMT</pubDate></item><item><title><![CDATA[Reply to Problems after upgrade on Thu, 29 Sep 2011 02:39:55 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">I think the problem was that fop2admin was not updated, right? I will update the README file..</p>
<p dir="auto">for other users, if you use fop2admin and there is an updated fop2 and updated fop2admin, you will need to update both.</p>
<p dir="auto">Best regards,</p>
]]></description><link>http://localhost:4567/post/4015</link><guid isPermaLink="true">http://localhost:4567/post/4015</guid><dc:creator><![CDATA[nicolas]]></dc:creator><pubDate>Thu, 29 Sep 2011 02:39:55 GMT</pubDate></item></channel></rss>