[GH-ISSUE #132] ViMbTool (cronjobs) cannot modify header #100

Closed
opened 2026-02-26 09:35:53 +03:00 by kerem · 5 comments
Owner

Originally created by @kenayagi on GitHub (Mar 20, 2015).
Original GitHub issue: https://github.com/opensolutions/ViMbAdmin/issues/132

I'm using ViMbAdmin 3.0.8 on Debian Wheezy. The system had been setup freshly from scratch.

It seems that ./bin/vimbtool.php can't work properly:

root@mail:~# /opt/vimbadmin/bin/vimbtool.php -a mailbox.get-sizes -d
Module:
Controller: mailbox
Action:     get-sizes

PHP Warning:  Cannot modify header information - headers already sent by (output started at /opt/vimbadmin/bin/vimbtool.php:108) in /opt/vimbadmin/vendor/zendframework/zendframework1/library/Zend/Controller/Response/Abstract.php on line 360

Warning: Cannot modify header information - headers already sent by (output started at /opt/vimbadmin/bin/vimbtool.php:108) in /opt/vimbadmin/vendor/zendframework/zendframework1/library/Zend/Controller/Response/Abstract.php on line 360

The same happens for

root@mail:~# /opt/vimbadmin/bin/vimbtool.php -a archive.archive-pendings -d
root@mail:~# /opt/vimbadmin/bin/vimbtool.php -a archive.delete-pendings -d
root@mail:~# /opt/vimbadmin/bin/vimbtool.php -a archive.restore-pendings -d

Could you give me a tip on how to solve it?

Thanks.

Originally created by @kenayagi on GitHub (Mar 20, 2015). Original GitHub issue: https://github.com/opensolutions/ViMbAdmin/issues/132 I'm using ViMbAdmin 3.0.8 on Debian Wheezy. The system had been setup freshly from scratch. It seems that ./bin/vimbtool.php can't work properly: ``` root@mail:~# /opt/vimbadmin/bin/vimbtool.php -a mailbox.get-sizes -d Module: Controller: mailbox Action: get-sizes PHP Warning: Cannot modify header information - headers already sent by (output started at /opt/vimbadmin/bin/vimbtool.php:108) in /opt/vimbadmin/vendor/zendframework/zendframework1/library/Zend/Controller/Response/Abstract.php on line 360 Warning: Cannot modify header information - headers already sent by (output started at /opt/vimbadmin/bin/vimbtool.php:108) in /opt/vimbadmin/vendor/zendframework/zendframework1/library/Zend/Controller/Response/Abstract.php on line 360 ``` The same happens for ``` root@mail:~# /opt/vimbadmin/bin/vimbtool.php -a archive.archive-pendings -d root@mail:~# /opt/vimbadmin/bin/vimbtool.php -a archive.delete-pendings -d root@mail:~# /opt/vimbadmin/bin/vimbtool.php -a archive.restore-pendings -d ``` Could you give me a tip on how to solve it? Thanks.
kerem closed this issue 2026-02-26 09:35:54 +03:00
Author
Owner

@liayn commented on GitHub (May 27, 2015):

Would be interested as well

<!-- gh-comment-id:105991191 --> @liayn commented on GitHub (May 27, 2015): Would be interested as well
Author
Owner

@barryo commented on GitHub (May 30, 2015):

Where did you find this:

/opt/vimbadmin/bin/vimbtool.php -a mailbox.get-sizes

As the correct version is:

/opt/vimbadmin/bin/vimbtool.php -a mailbox.cli-get-sizes

All the CLI commands have a cli- prefix.

Please let me know where you found the incorrect version so I can update the documentation.

<!-- gh-comment-id:107021923 --> @barryo commented on GitHub (May 30, 2015): Where did you find this: > /opt/vimbadmin/bin/vimbtool.php -a mailbox.get-sizes As the correct version is: > /opt/vimbadmin/bin/vimbtool.php -a mailbox.cli-get-sizes All the CLI commands have a cli- prefix. Please let me know where you found the incorrect version so I can update the documentation.
Author
Owner
<!-- gh-comment-id:107952498 --> @liayn commented on GitHub (Jun 2, 2015): https://github.com/opensolutions/ViMbAdmin/blob/master/bin/crons/vimbadmin
Author
Owner

@barryo commented on GitHub (Jun 2, 2015):

Thanks, fixed.

<!-- gh-comment-id:107953379 --> @barryo commented on GitHub (Jun 2, 2015): Thanks, fixed.
Author
Owner

@liayn commented on GitHub (Jun 2, 2015):

Thanks.

Maybe you can also take care of the broken schema stuff, which prevents a successful upgrade (installation?) currently, when using a different DB name.
is already done. sorry,

<!-- gh-comment-id:107954056 --> @liayn commented on GitHub (Jun 2, 2015): Thanks. ~~Maybe you can also take care of the broken schema stuff, which prevents a successful upgrade (installation?) currently, when using a different DB name.~~ is already done. sorry,
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ViMbAdmin-opensolutions#100
No description provided.