Obtaining update status spits out a long series of warnings



  • I also tried installing a machine completely from scratch and restoring the config. This is only happening on one of my firewalls. Have gone over the config line by line comparing to the backup carp cluster node to this firewall and cannot tell what may be causing it.

    2.1-RC2 (amd64) 
    built on Sun Sep 8 09:48:34 EDT 2013 
    FreeBSD 8.3-RELEASE-p10
    
    Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/services.inc:2249) in /usr/local/www/guiconfig.inc on line 48 
    Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/services.inc:2249) in /usr/local/www/guiconfig.inc on line 49 
    Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/services.inc:2249) in /usr/local/www/guiconfig.inc on line 50 
    Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/services.inc:2249) in /usr/local/www/guiconfig.inc on line 51 
    Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/services.inc:2249) in /usr/local/www/guiconfig.inc on line 52 
    Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/services.inc:2249) in /usr/local/www/guiconfig.inc on line 55 
    Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /etc/inc/services.inc:2249) in /etc/inc/auth.inc on line 1357
    
    You are on the latest version.
    

    Any suggestions where to look?



  • Strange the file /etc/inc/services.inc should have just 2222 lines: https://github.com/pfsense/pfsense/blob/RELENG_2_1/etc/inc/services.inc

    Could you go to: Diagnostic->Edit File and load the file  /etc/inc/services.inc
    Copy it to an editor and see whats in line 2249



  • That was one of the first things I checked. services.inc on that particular machine ends at line 2221. Looking at it with vi from the ssh console.



  • try to delete the last 2 lines: "?>" and the empty line afterwards.

    if there is any strange character after "?>" e.g. space or something that is not displayed probably it is send as output and this error can occur.


Log in to reply