HB-6680 - export_horde_calendars_to_ics error
Hello,
When I run the calendar export script /usr/local/cpanel/scripts/export_horde_calendars_to_ics like this:
/usr/local/cpanel/scripts/export_horde_calendars_to_ics --user=user --out=/home/user/work/mig/cal
I get errors:
Argument "9999-12-31 00:00:00" isn't numeric in numeric ne (!=) at /usr/local/cpanel/scripts/export_horde_calendars_to_ics line 157.
Argument "9999-12-31 00:00:00" isn't numeric in numeric ne (!=) at /usr/local/cpanel/scripts/export_horde_calendars_to_ics line 157.
Argument "9999-12-31 00:00:00" isn't numeric in numeric ne (!=) at /usr/local/cpanel/scripts/export_horde_calendars_to_ics line 157.
Argument "9999-12-31 00:00:00" isn't numeric in numeric ne (!=) at /usr/local/cpanel/scripts/export_horde_calendars_to_ics line 157.
Argument "9999-12-31 00:00:00" isn't numeric in numeric ne (!=) at /usr/local/cpanel/scripts/export_horde_calendars_to_ics line 157.
Argument "2013-01-21 00:00:00" isn't numeric in numeric ne (!=) at /usr/local/cpanel/scripts/export_horde_calendars_to_ics line 157.
Not a HASH reference at /usr/local/cpanel/scripts/export_horde_calendars_to_ics line 89.
It looks like one error for each mailbox in horde
Any idea on how to get export_horde_calendars_to_ics to work or what this means?
So it seems that line 157 is taking issue with the value:
Argument "9999-12-31 00:00:00" isn't numeric in numeric ne (!=) at /usr/local/cpanel/scripts/export_horde_calendars_to_ics line 157.
Argument "2013-01-21 00:00:00" isn't numeric in numeric ne (!=) at /usr/local/cpanel/scripts/export_horde_calendars_to_ics line 157.
See attached. The Argument "9999-12-31 00:00:00" in the ne (!=) is not != '99991231'; in comparison
Either the script has a bug or it is encountering unexpected data format.
-03-06 at 3.06.33 PM.png">81701
-03-06 at 3.06.43 PM.png">81705
-
Hey there! For any Horde cases, we'd really like to see a ticket created so we can investigate this on a server having the issues. Could you submit a ticket and then post the number here? 0 -
I have a ticket open, #94538679, so far not very helpful. 0 -
It looks like we haven't gained access to the system just yet, so that isn't too surprising. I'm following along on my end now. 0 -
Right, Like I said, not helpful. I explained you system is throwing an error looking for port 22 when a none standard port is clearly set. I also, ask them to stay focused on the calendar export. Please tell me the next steps. I can do many things. I get no guidance from support. The error is the script encountering data it is not expecting. So something else need to be done. 0 -
Here is where we are now: [QUOTE]It appears there may be a patch for the issue you are experiencing; however, it has not been officially pushed out. Before I make any changes to the scripts, I want to send this ticket to our level 2 analysts to review and see if we are able to apply the patch or if there is another solution. 0 -
So far support is looking and keep escalating. They say it is an issue unique to the user account since other accounts export, however, no other accounts have any calendar data or contact data. 0 -
This has caused some fun internal discussion for sure. I see it's still being worked on today, so hopefully our team will be able to find more details soon. 0 -
Yes, They really seem to be trying. We have them escalating the escalations. I think we are III now. Is there any way to get a partial export and log those items that cannot export due to offending data? If we could do that then I can give the users a partial calendar while we work on getting the offending items to export. Is that possible? Can you share win me where the SQL lite db lives on the server? 0 -
I don't have any additional details on my end that you wouldn't have through the ticket. 0 -
I don't have any additional details on my end that you wouldn't have through the ticket.
Thanks. I thought I sneak in a question here. :-)0 -
I see our team was able to confirm the behavior and we have filed case HB-6680 with our developers. I'm tracking that now and I'll be sure to update this page as I get more details. 0 -
I see our team was able to confirm the behavior and we have filed case HB-6680 with our developers. I'm tracking that now and I'll be sure to update this page as I get more details.
Nice!0 -
Well I was told they files a case HB-6680 with your developers and they have NOT ETA ON action. Meaning they may never get to fixing this. I may loose a client over this. 0 -
When a case is filed with the developers it means we've found an issue within the product itself that can't be resolved without fixing code. That means a development team needs to take on the work, find a solution, test it, have QA test it, and then get it included in a future cPanel release. This process is not always quick, and sometimes the issues get superseded by future development work. I understand that the possibility of losing a client due to the malfunctioning function is a serious concern, and I have conveyed this to our development team, along with a link to this specific Forums post. In general, we do not provide ETAs unless we are 100% certain that they will be met. From our experience, setting unrealistic deadlines leads to disappointment if they are not met, no matter the reason. If we have information on when a solution will be implemented, I'll be sure to share that here as I'm following along with the case now. 0 -
When a case is filed with the developers it means we've found an issue within the product itself that can't be resolved without fixing code. That means a development team needs to take on the work, find a solution, test it, have QA test it, and then get it included in a future cPanel release. This process is not always quick, and sometimes the issues get superseded by future development work. I understand that the possibility of losing a client due to the malfunctioning function is a serious concern, and I have conveyed this to our development team, along with a link to this specific Forums post. In general, we do not provide ETAs unless we are 100% certain that they will be met. From our experience, setting unrealistic deadlines leads to disappointment if they are not met, no matter the reason. If we have information on when a solution will be implemented, I'll be sure to share that here as I'm following along with the case now.
I understand that. But I no on is reply to intermediate help either. I keep asking, Is there any way to get a partial export and log those items that cannot export due to offending data? If we could do that then I can give the users a partial calendar while we work on getting the offending items to export. Can we do something more to get some data to the user/client instead of just saying yes, we see there is an issue. We have no idea if or when it will be addressed. can we back grade the host88 server from 108 to 106? Maybe do a manual export from when horde was active on v106?0 -
Well we are now in limbo. No eta and no clear way to know when this is fixed either. I looked at the pearl export script and could see the section that was causing the error was the attendee section. commenting out that section in a copy of the script allowed me export all the data to ICS less attendees for any event. I think that better than nothing. I find it odd that no at cpanel would look at the script to see if we could get a partial export. I was told no, it dies before exporting. Gee really? Thanks! I had hoped this would be taken more seriously, but I guess you get what you pay for and $60 a month for server licenses does not go that far at cpanel. Anyway, I feel a rant coming on ... I'll go now before I post things I can't take back. Hope most have a better experience. 0 -
Our team was able to get that article created so you can follow along without a ticket. I wish I had a more solid plan of how the dev work is going to look, but I just don't. I can say with all the Horde calendar things happening right now, it's already been looked at by the team, and I'll be sure to post updates here as well as I hear things, or if a fix gets tagged to a certain cPanel version. 0 -
Thanks for the update. I'm following the article. :) Funny I was able to get a partial export and now the target server is having roundcube issues creating a calendar. I opened a tick on this too. I have other servers that run same version of cpanel that can create calendars but the target server will not create a calendar. So I'm stuck again. :( Thanks for your update. :) 0 -
Update - while this doesn't indicate any ETA, I do see it has been assigned to a development team. 0 -
Progress! Moving forward! :) 0
Please sign in to leave a comment.
Comments
21 comments